From: Valdis.Kletnieks@vt.edu
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.1-rc10
Date: Sat, 22 Oct 2011 01:31:32 -0400 [thread overview]
Message-ID: <9983.1319261492@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 22 Oct 2011 06:08:31 +0300." <CA+55aFzLTjB+CwB7MQNh+p0pjSrFd=pBFDcA=GxMY4HJhQokUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Sat, 22 Oct 2011 06:08:31 +0300, Linus Torvalds said:
> It's ALWAYS that easy. Your argument is totally flawed. The only one
> who should be busy during the merge window is *me*. If you're busy
> during th emerge window, you're doing something wrong.
Actually, the question was "Are there enough Linus cycles to do KS
and all the merges in 2 weeks?". ;)
(And when I wrote "and everybody will be busy at KS", I didn't mean "Ted T'So
won't have his tree ready to pull", I meant "Linus finally gets back to his
hotel room and tries to merge Ted's tree, hits some really weird merge issue,
and Ted's not answering his e-mail or his phone because he's still discussing
something over beer and pizza down at the hotel bar, so that's *another* merge
that waits till the next day..."
> Seriously. I'm not going to extend the merge window at all. Because we
> extended the time when you could do your actual work already - if you
> waited until the merge window to do work, then I don't want to see
> your pull request ANYWAY. I'll take it the *next* merge window, thank
> you very much.
OK, so Linus will get some sleep after -rc1, which will be the customary
2 weeks. I can deal with that answer. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-22 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 4:19 Linux 3.1-rc10 Linus Torvalds
2011-10-21 20:15 ` Valdis.Kletnieks
2011-10-22 3:08 ` Linus Torvalds
2011-10-22 5:31 ` Valdis.Kletnieks [this message]
2011-10-23 0:47 ` Linus Torvalds
2011-10-23 6:16 ` Dave Airlie
2011-10-23 7:42 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2011-10-18 7:31 Sedat Dilek
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=9983.1319261492@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.