From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
dhowells@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.28-rc8
Date: Fri, 12 Dec 2008 08:54:15 +0100 [thread overview]
Message-ID: <20081212075414.GF24323@8bytes.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0812112138510.3340@localhost.localdomain>
On Thu, Dec 11, 2008 at 09:40:21PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 11 Dec 2008, David Miller wrote:
>
> > From: David Howells <dhowells@redhat.com>
> > Date: Thu, 11 Dec 2008 15:29:06 +0000
> >
> > > Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > >
> > > > (a) just make the -rc's go on a few more weeks, and do 2.6.28 after xmas
> > > >
> > > > I like this, because alledgely people are debugging things, and we'd
> > > > get a more stable 2.6.28.
> > >
> > > Which would perhaps mean that the merge window is open during LCA, which will
> > > be inconvenient for some people. On the other hand, it might put the culprits
> > > where you can lay your hands on them.
> >
> > That happened in Melbourne and it wasn't pleasant. Instead
> > of enjoying talks at the conference some of us were stressing
> > out on our laptops dealing with our merges instead.
>
> Yes. I definitely want to close the 29 merge window before LCA. In fact, I
> want to close it far enough before that we can fix up any worst issues.
>
> Which does argue for opening it up during the holidays, I guess.
You can do a release around 29th/30th December. This gives the people
who are on vacation until the new year still a week for merging stuff
and the merge window closes 4-5 days before people are leaving for
LCA.
Joerg
next prev parent reply other threads:[~2008-12-12 7:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 1:04 Linux 2.6.28-rc8 Linus Torvalds
2008-12-11 2:37 ` Gabriel C
2008-12-11 7:19 ` Eric Anholt
2008-12-11 16:07 ` Frans Pop
2008-12-11 16:22 ` Linus Torvalds
2008-12-11 16:35 ` Ingo Molnar
2008-12-11 17:05 ` Linus Torvalds
2008-12-11 20:36 ` Ingo Molnar
2008-12-11 20:46 ` Pekka Enberg
2008-12-11 21:34 ` Suresh Siddha
2008-12-12 8:24 ` Ingo Molnar
2008-12-12 15:57 ` Arjan van de Ven
2008-12-12 16:11 ` Linus Torvalds
2008-12-13 17:15 ` Arjan van de Ven
2008-12-16 22:34 ` Ingo Molnar
2008-12-11 5:09 ` Arjan van de Ven
2008-12-11 7:57 ` Nick Piggin
2008-12-11 8:07 ` Andrew Morton
2008-12-11 8:45 ` Nick Piggin
2008-12-12 3:02 ` Andrew Morton
2008-12-12 3:07 ` Nick Piggin
2008-12-12 3:39 ` Andrew Morton
2008-12-11 8:06 ` Willy Tarreau
2008-12-11 8:40 ` Joerg Roedel
2008-12-11 22:57 ` Theodore Tso
2008-12-11 23:12 ` Mike Travis
2008-12-11 9:26 ` Jean Delvare
2008-12-11 10:38 ` Frederik Deweerdt
2008-12-11 16:59 ` Andrew Morton
2008-12-11 13:00 ` Sam Ravnborg
2008-12-11 13:23 ` Paolo Ciarrocchi
2008-12-11 13:44 ` Alexey Zaytsev
2008-12-11 13:48 ` Ingo Molnar
2008-12-11 15:20 ` Pavel Machek
2008-12-11 15:29 ` David Howells
2008-12-12 3:19 ` David Miller
2008-12-12 5:40 ` Linus Torvalds
2008-12-12 7:54 ` Joerg Roedel [this message]
2008-12-12 15:48 ` Alan Cox
2008-12-11 20:12 ` Rafael J. Wysocki
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=20081212075414.GF24323@8bytes.org \
--to=joro@8bytes.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox