From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.24
Date: Thu, 24 Jan 2008 15:41:08 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.1.00.0801241529440.15329@hp.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0801241506500.15329@hp.linux-foundation.org>
On Thu, 24 Jan 2008, Linus Torvalds wrote:
>
> The release is out there (both git trees and as tarballs/patches), and for
> the next week many kernel developers will be at (or flying into/out of)
> LCA in Melbourne, so let's hope it's a good one.
Since I already had two kernel developers asking about the merge window
and whether people (including me) traveling will impact it, the plan right
now is to keep the impact pretty minimal. So yes, it will probably extend
the window from the regular two weeks, but *hopefully* not by more than a
few days.
I'm going to try to merge at least some stuff while I'm in Melbourne, and
I'd expect that most of the stuff that happens during LCA is code that is
already pending to be merged (that's how the merge window is _supposed_ to
work, after all, but with the 2.6.24 release cycle being longer than usual
I suspect it's actually true in practice too).
And the second week of the merge window I'll be back again.
If I have bad bandwidth or am just goofing off during LCA, or if I end up
being too jetlagged to merge well after, that will obviously push out
things. And the same thing obviously goes for any other maintainer in the
same condition.
I'd hope that the git users to be in fairly good condition (with hopefully
much of the stuff pending for 2.6.25 ready to go), and would worry more
about people like Andrew in particular. So let's see how this works out.
In short: I'm hoping that there won't be a big impact, but hey, let's be
flexible. Who knows what happens..
Linus
next prev parent reply other threads:[~2008-01-24 23:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 23:17 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds [this message]
2008-01-25 9:10 ` Giacomo A. Catenazzi
2008-01-25 9:58 ` Valdis.Kletnieks
2008-01-25 11:58 ` Rafael J. Wysocki
2008-01-25 12:34 ` Giacomo A. Catenazzi
2008-01-25 23:50 ` Stefan Richter
2008-01-26 0:42 ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26 3:28 ` Valdis.Kletnieks
2008-01-26 13:31 ` using LKML for subsystem development Stefan Richter
2008-01-27 7:37 ` Valdis.Kletnieks
2008-01-26 11:28 ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07 ` using LKML for subsystem development David Miller
2008-01-26 14:45 ` Stefan Richter
2008-01-26 14:25 ` Stefan Richter
2008-02-01 9:40 ` Ingo Molnar
2008-02-01 19:53 ` Stefan Richter
2008-01-26 3:19 ` Linux 2.6.24 Valdis.Kletnieks
2008-01-25 11:35 ` Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30 ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt
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.1.00.0801241529440.15329@hp.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--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
Powered by JetHome