From: Linus Torvalds <torvalds@linux-foundation.org>
To: Daniel Walker <dwalker@fifo99.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.33 released
Date: Wed, 24 Feb 2010 12:50:10 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002241247130.4513@localhost.localdomain> (raw)
In-Reply-To: <1267042804.30876.37.camel@c-dwalke-linux.qualcomm.com>
On Wed, 24 Feb 2010, Daniel Walker wrote:
>
> Last merge window you mention you might do a one week merge window this
> time around, are you still planning to do that?
No. But I might do a ten-to-twelve day thing or something like that - just
to make sure that anybody who tries to game the system and send their
merge request late will get summarily ignored.
So I'm going to stop being so predictable that people can tell that
exactly two weeks after the last release is where the merge window closes,
and if people want to make sure their stuff merged, I had better have a
merge request in my inbox earlier than thirteen days after the release.
Linus
prev parent reply other threads:[~2010-02-24 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 20:06 Linus Torvalds
2010-02-24 20:20 ` Daniel Walker
2010-02-24 20:50 ` Linus Torvalds [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=alpine.LFD.2.00.1002241247130.4513@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=dwalker@fifo99.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®