linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: A fs-next branch
Date: Mon, 20 May 2024 22:38:16 +0100	[thread overview]
Message-ID: <ZkvCyB1-WpxH7512@casper.infradead.org> (raw)
In-Reply-To: <20240520132326.52392f8d@canb.auug.org.au>

On Mon, May 20, 2024 at 01:23:26PM +1000, Stephen Rothwell wrote:
> Hi Willy,
> 
> Sorry for the slow response.

No problem; I figure you get one week off every ten weeks or so ...

> On Tue, 14 May 2024 23:57:36 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> >
> > 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?
> 
> How would this be different from what happens at the moment with all
> the separate file system trees and the various "vfs" trees?  I can
> include any tree.

As I understand the structure of linux-next right now, you merge one
tree after another in some order which isn't relevant to me, so I have no
idea what it is.  What we're asking for is that we end up with a branch
in your tree called fs-next that is:

 - Linus's tree as of that day
 - plus the vfs trees
 - plus xfs, btrfs, ext4, nfs, cifs, ...

but not, eg, graphics, i2c, tip, networking, etc

How we get that branch is really up to you; if you want to start by
merging all the filesystem trees, tag that, then continue merging all the
other trees, that would work.  If you want to merge all the filesystem
trees to fs-next, then merge the fs-next tree at some point in your list
of trees, that would work too.

Also, I don't think we care if it's a branch or a tag.  Just something
we can call fs-next to all test against and submit patches against.
The important thing is that we get your resolution of any conflicts.

There was debate about whether we wanted to include mm-stable in this
tree, and I think that debate will continue, but I don't think it'll be
a big difference to you whether we ask you to include it or not?

  parent reply	other threads:[~2024-05-20 21:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 22:57 A fs-next branch Matthew Wilcox
2024-05-20  3:23 ` Stephen Rothwell
2024-05-20  4:58   ` Theodore Ts'o
2024-05-20 21:38   ` Matthew Wilcox [this message]
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=ZkvCyB1-WpxH7512@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).