mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: charter for -next
Date: Sun, 4 May 2008 17:56:12 +1000	[thread overview]
Message-ID: <20080504175612.07b0b0a0.sfr@canb.auug.org.au> (raw)
In-Reply-To: <481C3AA2.6020809@s5r6.in-berlin.de>

[-- 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 --]

      parent reply	other threads:[~2008-05-04  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-03 10:12 Stefan Richter
2008-05-03 13:18 ` Jeff Garzik
2008-05-04  7:56 ` Stephen Rothwell [this message]

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=20080504175612.07b0b0a0.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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®