From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-fsdevel@vger.kernel.org
Subject: A fs-next branch
Date: Tue, 14 May 2024 23:57:36 +0100 [thread overview]
Message-ID: <ZkPsYPX2gzWpy2Sw@casper.infradead.org> (raw)
Hi Stephen,
At LSFMM we're talking about the need to do more integrated testing with
the various fs trees, the fs infrastructure and the vfs. We'd like to
avoid that testing be blocked by a bad patch in, say, a graphics driver.
A solution we're kicking around would be for linux-next to include a
'fs-next' branch which contains the trees which have opted into this
new branch. Would this be tremendously disruptive to your workflow or
would this be an easy addition?
next reply other threads:[~2024-05-14 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 22:57 Matthew Wilcox [this message]
2024-05-20 3:23 ` A fs-next branch Stephen Rothwell
2024-05-20 4:58 ` Theodore Ts'o
2024-05-20 21:38 ` Matthew Wilcox
2024-05-27 23:16 ` Stephen Rothwell
2024-05-29 4:35 ` Stephen Rothwell
2024-05-29 11:12 ` Christian Brauner
2024-05-30 23:50 ` Stephen Rothwell
2024-06-10 13:15 ` Andreas Gruenbacher
2024-06-10 22:16 ` Stephen Rothwell
2024-06-11 3:53 ` Matthew Wilcox
2024-06-11 22:51 ` Stephen Rothwell
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=ZkPsYPX2gzWpy2Sw@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).