Hi Matthew, On Mon, 20 May 2024 22:38:16 +0100 Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > 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? OK, I can see how to do that. I will start on it tomorrow. The plan is that you will end up with a branch (fs-next) in the linux-next tree that will be a merge of the above trees each day and I will merge it into the -next tree as well. -- Cheers, Stephen Rothwell
Attachment:
pgpaTjrgtaXie.pgp
Description: OpenPGP digital signature
