From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcachefs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: weekly bcachefs meeting, 1PM EST
Date: Mon, 22 Apr 2024 17:04:02 -0400 [thread overview]
Message-ID: <xeezdsisgeku5sjoqlpgkijgxxsqcy6lu5fz563khmr72armns@xu2jqclpz2rv> (raw)
Shoot me an email if you'd like to come, and something about what you're
interested in or would like to talk about.
Good topics:
- bugs you're working on, behaviour that needs explaining, or
better introspection/debug tooling
- short code walkthroughs
- short, focused code review
- design questions for things being actively worked on
- support issues that may need my attention
i.e., let's keep everyone abreast of each other's work and help each
other stay productive.
And as always, the best place to meet and discuss is on IRC. We've now
got two channels:
irc.oftc.net#bcache - the general and oldest channel (hence the name);
this is more user focused - debugging, some support, as users popping up
saying "hey, I noticed something interesting".
#bcachefs-dev - this one is dev focused; it's quieter so that us devs
can say "here's this thing I'm currently banging my head against" and
hopefully get a response :)
Cheers,
Kent
reply other threads:[~2024-04-22 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xeezdsisgeku5sjoqlpgkijgxxsqcy6lu5fz563khmr72armns@xu2jqclpz2rv \
--to=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).