mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, sfrench@us.ibm.com,
	swhiteho@redhat.com, stefanr@s5r6.in-berlin.de, jeff@garzik.org,
	ralf@linux-mips.org, drzeus-list@drzeus.cx, jack@ucw.cz,
	cbou@mail.ru, jens.axboe@oracle.com, ericvh@gmail.com,
	wim@iguana.be, chris@zankel.net, nico@cam.org, clameter@sgi.com,
	ezk@cs.sunysb.edu, linux-kernel@vger.kernel.org
Subject: Re: git trees which are not yet in linux-next
Date: Tue, 6 May 2008 14:41:11 +1000	[thread overview]
Message-ID: <20080506144111.43736d63.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0805052136530.5570@sbz-30.cs.Helsinki.FI>

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

Hi Pekka,

On Mon, 5 May 2008 21:41:53 +0300 (EEST) Pekka J Enberg <penberg@cs.helsinki.fi> 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@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-05-06  4:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 22:12 Andrew Morton
2008-05-02 22:20 ` Jeff Garzik
2008-05-02 22:33   ` Andrew Morton
2008-05-03  4:33     ` Stephen Rothwell
2008-05-03  4:54     ` Jeff Garzik
2008-05-02 22:42 ` Andrew Morton
2008-05-03  1:19   ` Stefan Richter
2008-05-03  1:34     ` Andrew Morton
2008-05-03  4:52       ` Jeff Garzik
2008-05-03  8:46         ` Stefan Richter
2008-05-05  0:18           ` Stephen Rothwell
2008-05-03  1:11 ` Stefan Richter
2008-05-03  1:18   ` Andrew Morton
2008-05-05 16:52 ` Liam Girdwood
2008-05-05 17:57   ` Andrew Morton
2008-05-06  4:45     ` Stephen Rothwell
2008-05-06  5:50       ` Andrew Morton
2008-05-06  7:18         ` Stephen Rothwell
2008-05-05 18:16 ` Pekka Enberg
2008-05-05 18:31   ` Andrew Morton
2008-05-05 18:41     ` Pekka J Enberg
2008-05-05 19:40       ` Stefan Richter
2008-05-05 21:11       ` Daniel Hazelton
2008-05-06  4:41       ` Stephen Rothwell [this message]
2008-05-06  4:43     ` Stephen Rothwell
2008-05-13  6:36 ` Pierre Ossman
2008-05-13  7:00   ` Stephen Rothwell
2008-05-13 10:47     ` Pierre Ossman
2008-05-13 12:33       ` 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=20080506144111.43736d63.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=cbou@mail.ru \
    --cc=chris@zankel.net \
    --cc=clameter@sgi.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=ericvh@gmail.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=jack@ucw.cz \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=ralf@linux-mips.org \
    --cc=sfrench@us.ibm.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=swhiteho@redhat.com \
    --cc=wim@iguana.be \
    /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
all inboxes | Powered by JetHome®