[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130711135522.GN8530@agk-dp.fab.redhat.com>
Date: Thu, 11 Jul 2013 14:55:22 +0100
From: Alasdair G Kergon <agk@...hat.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Alasdair G Kergon <agk@...hat.com>,
Yann Droneaud <ydroneaud@...eya.com>,
Mike Snitzer <snitzer@...hat.com>,
Robin Dong <sanbai@...bao.com>, linux-kernel@...r.kernel.org,
Jim Ramsay <jim_ramsay@...l.com>, dm-devel@...hat.com,
Mikulas Patocka <mpatocka@...hat.com>,
"Jun'ichi Nomura" <j-nomura@...jp.nec.com>,
Rob Herring <robherring2@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Milan Broz <gmazyland@...il.com>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [dm-devel] [git pull] device-mapper changes for 3.11
On Thu, Jul 11, 2013 at 04:20:40PM +1000, Stephen Rothwell wrote:
> Alistair, is there some reason that you cannot maintain some relatively
> stable git tree for me to fetch (instead of the quilt series).
Well Mike Snitzer is becoming a joint maintainer and this also requires
changes to the workflow so watch this space.
> Also,
> there is not real reason to keep rebasing this stuff (especially just
> before sending it to Linus).
Most of the time the patches are decoupled from the rest of the tree
and the final linux-next kernel is the same regardless of where the
quilt tree is attached. I maintain a single sequence of patches
where the ones ready for upstream float up to the top and the
linux-next export is a by-product and not the primary output.
Anyway, like I say, we'll be changing things during the next couple of
cycles and we'll bear your suggestions in mind.
Alasdair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists