From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [weekly bcachefs cabal] tuesday, 1PM EST
Date: Fri, 16 Feb 2024 17:13:27 -0500 [thread overview]
Message-ID: <l75bqikzjjrtehvkkv7jzsr4ei5ingz6ygxwjnt4tv6otqexdq@cbr5brx7xzmo> (raw)
been a bit since I've sent out an announce for this, and there's new
names popping up on the list contributing fixes, so...
chat about bugs, complain about code you're staring at, the usual
filesystem bullshit
shoot me an email for an invite
reply other threads:[~2024-02-16 22:13 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=l75bqikzjjrtehvkkv7jzsr4ei5ingz6ygxwjnt4tv6otqexdq@cbr5brx7xzmo \
--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).