From: Matthew Wilcox <willy@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-bcachefs@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] bcachefs
Date: Tue, 7 Mar 2023 07:25:15 +0000 [thread overview]
Message-ID: <ZAbm2zTX83Cfl2SJ@casper.infradead.org> (raw)
In-Reply-To: <Y/ZxFwCasnmPLUP6@moria.home.lan>
On Wed, Feb 22, 2023 at 02:46:31PM -0500, Kent Overstreet wrote:
> I'd like to talk more about where things are at, long term goals, and
> finally upstreaming this beast.
We don't have any rules about when we decide to upstream a new filesystem.
There are at least four filesystems considering inclusion right now;
bcachefs, SSDFS, composefs and nvfs. Every new filesystem imposes
certain costs on other developers (eg those who make sweeping API changes,
*cough*). I don't think we've ever articulated a clear set of criteria,
and maybe we can learn from the recent pain of accepting ntfs3 in the
upstream kernel.
next prev parent reply other threads:[~2023-03-07 7:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 19:46 [LSF/MM/BPF TOPIC] bcachefs Kent Overstreet
2023-03-07 5:01 ` Darrick J. Wong
2023-03-07 6:12 ` Kent Overstreet
2023-03-07 7:25 ` Matthew Wilcox [this message]
2023-03-07 7:59 ` Kent Overstreet
-- strict thread matches above, loose matches on Subject: below --
2024-01-01 22:56 Kent Overstreet
2024-01-02 8:02 ` Viacheslav Dubeyko
2024-01-02 16:05 ` Kent Overstreet
2024-01-03 7:39 ` Viacheslav Dubeyko
2024-01-03 17:52 ` Kent Overstreet
2024-01-03 19:22 ` Carl E. Thompson
2024-01-03 22:26 ` Kent Overstreet
2024-01-04 7:43 ` Viacheslav Dubeyko
2022-02-16 7:44 Kent Overstreet
2021-06-02 23:07 Kent Overstreet
2021-06-30 18:18 ` Dan Robertson
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=ZAbm2zTX83Cfl2SJ@casper.infradead.org \
--to=willy@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 NNTP newsgroup(s).