From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: RMK closing tree to patches *this* weekend
Date: Mon, 17 May 2010 16:10:36 +0100 [thread overview]
Message-ID: <20100517151036.GE29422@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1005170858290.12758@xanadu.home>
On Mon, May 17, 2010 at 09:04:53AM -0400, Nicolas Pitre wrote:
> I don't mind not seeing it in your tree for your initial batch to
> Linus as long as I know you'll accept it sometimes for this merge window.
The other thing to point out is that the merge windows are now much
more unpredictable.
The last merge window was 12 days long, rather than the usual 14. With
Linus' statement about the two week window being too predictable, I would
not be surprised if this merge window was about 7 days instead.
What this means overall is that it becomes much harder to sanely plan
stuff either for the lead up to the merge window, or during the merge
window itself.
Therefore, this "initial batch" is most likely to become "only batch"
since it's no longer possible to be reasonably ensure that there will
be a merge window open in the second week.
next prev parent reply other threads:[~2010-05-17 15:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 23:02 RMK closing tree to patches *this* weekend Russell King - ARM Linux
2010-05-14 0:35 ` Ben Dooks
2010-05-14 9:20 ` Russell King - ARM Linux
2010-05-14 0:58 ` Jassi Brar
2010-05-14 9:24 ` Russell King - ARM Linux
2010-05-14 14:21 ` Jassi Brar
2010-05-14 2:09 ` Ming Lei
2010-05-14 9:27 ` Russell King - ARM Linux
2010-05-17 9:03 ` Russell King - ARM Linux
2010-05-17 13:04 ` Nicolas Pitre
2010-05-17 13:08 ` Russell King - ARM Linux
2010-05-17 15:10 ` Russell King - ARM Linux [this message]
2010-05-17 15:44 ` Will Deacon
2010-05-17 16:18 ` Russell King - ARM Linux
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=20100517151036.GE29422@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).