From: Jeff Garzik <jeff@garzik.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: charter for -next
Date: Sat, 03 May 2008 09:18:42 -0400 [thread overview]
Message-ID: <481C6632.8070506@garzik.org> (raw)
In-Reply-To: <481C3AA2.6020809@s5r6.in-berlin.de>
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
next prev parent reply other threads:[~2008-05-03 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 10:12 charter for -next Stefan Richter
2008-05-03 13:18 ` Jeff Garzik [this message]
2008-05-04 7:56 ` 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=481C6632.8070506@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.