* charter for -next
@ 2008-05-03 10:12 Stefan Richter
2008-05-03 13:18 ` Jeff Garzik
2008-05-04 7:56 ` Stephen Rothwell
0 siblings, 2 replies; 3+ messages in thread
From: Stefan Richter @ 2008-05-03 10:12 UTC (permalink / raw)
To: Stephen Rothwell, Andrew Morton; +Cc: linux-next, linux-kernel
What should I ask myself before I commit something to the branch which
Stephen pulls into -next?
Is this ready to be pulled by Linus right now if he had a merge
window open today?
or
Is it likely that I will let Linus pull this when he opens his next
merge window? (Assuming I can roughly predict when this will be,
and what other work will likely be done until then, e.g. pending
reviewer feedback, or patches for related functionality which should
be bundled with the work in question...)
--
Stefan Richter
-=====-==--- -=-= ---==
http://arcgraph.de/sr/
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: charter for -next
2008-05-03 10:12 charter for -next Stefan Richter
@ 2008-05-03 13:18 ` Jeff Garzik
2008-05-04 7:56 ` Stephen Rothwell
1 sibling, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2008-05-03 13:18 UTC (permalink / raw)
To: Stefan Richter; +Cc: Stephen Rothwell, Andrew Morton, linux-next, linux-kernel
Stefan Richter wrote:
> What should I ask myself before I commit something to the branch which
> Stephen pulls into -next?
>
> Is this ready to be pulled by Linus right now if he had a merge
> window open today?
I was under the impression it was the above -- anything in linux-next
should be ready to be pulled by Linus. The maintainer considers those
changes "ready for next merge window."
Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: charter for -next
2008-05-03 10:12 charter for -next Stefan Richter
2008-05-03 13:18 ` Jeff Garzik
@ 2008-05-04 7:56 ` Stephen Rothwell
1 sibling, 0 replies; 3+ messages in thread
From: Stephen Rothwell @ 2008-05-04 7:56 UTC (permalink / raw)
To: Stefan Richter; +Cc: Andrew Morton, linux-next, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Hi Stefan,
On Sat, 03 May 2008 12:12:50 +0200 Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>
> What should I ask myself before I commit something to the branch which
> Stephen pulls into -next?
>
> Is this ready to be pulled by Linus right now if he had a merge
> window open today?
This is what I want ideally. So as stuff stabilises in subsystem trees,
it can be incorporated into linux-next and we can then figure out the
problems introduced by interactions with other subsystems.
> Is it likely that I will let Linus pull this when he opens his next
> merge window? (Assuming I can roughly predict when this will be,
> and what other work will likely be done until then, e.g. pending
> reviewer feedback, or patches for related functionality which should
> be bundled with the work in question...)
I suspect that this is what I got in some cases during the last
cycle :-) :-(
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-05-04 7:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-05-03 10:12 charter for -next Stefan Richter
2008-05-03 13:18 ` Jeff Garzik
2008-05-04 7:56 ` Stephen Rothwell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox