[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090722145917.055eddc1.sfr@canb.auug.org.au>
Date: Wed, 22 Jul 2009 14:59:17 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Lars Ellenberg <lars.ellenberg@...bit.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Philipp Reisner <philipp.reisner@...bit.com>,
Bart Van Assche <bart.vanassche@...il.com>,
Kyle Moffett <kyle@...fetthome.net>,
Christoph Hellwig <hch@...radead.org>,
Neil Brown <neilb@...e.de>,
Nikanth Karthikesan <knikanth@...e.de>,
Greg KH <gregkh@...e.de>,
James Bottomley <James.Bottomley@...senPartnership.com>,
Lars Marowsky-Bree <lmb@...e.de>,
Jens Axboe <jens.axboe@...cle.com>,
Dave Jones <davej@...hat.com>, Sam Ravnborg <sam@...nborg.org>,
drbd-dev@...ts.linbit.com, linux-kernel@...r.kernel.org,
linux-next@...r.kernel.org
Subject: Re: [Drbd-dev] [PATCH 00/16] drbd: a block device for HA clusters
Hi Lars,
On Tue, 21 Jul 2009 20:51:56 +0200 Lars Ellenberg <lars.ellenberg@...bit.com> wrote:
>
> Stephen: expect an explicit linux-next merge request
> within the next few days.
OK, just to be clear your tree should be based on Linus' tree (or some
other *stable*, non rebasing, tree - *not* linux-next).
[I guess your tree will fulfill all the following]
What I tell everyone: all patches/commits in the tree/series must
have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists