Re: git trees which are not yet in linux-next

From: Stephen Rothwell
Date: Tue May 06 2008 - 00:41:46 EST


Hi Pekka,

On Mon, 5 May 2008 21:41:53 +0300 (EEST) Pekka J Enberg <penberg@xxxxxxxxxxxxxx> wrote:
>
> Well, I only really have three kinds of patches: (1) testing, (2)
> for-linus asap (fixes in the middle of a release cycle) and (3) for-linus
> when the merge window opens. Up until now, I've put (1) in for-mm and
> after enough exposure (and no bug reports) they graduate into (2) or (3).
>
> So the problem here is where I put the patches in category (1)? If
> they can go into for-next, then for-mm can disappear. Stephen?

Stefan Richter is right: if they have passed your review and testing in
isolation, then they are allowed into -next for testing against other
subsystems. So (2), (3), and (1b) ... :-)

--
Cheers,
Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/

Attachment: pgp00000.pgp
Description: PGP signature