From: Mike Travis <travis@sgi.com>
To: Theodore Tso <tytso@mit.edu>, Joerg Roedel <joro@8bytes.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.28-rc8
Date: Thu, 11 Dec 2008 15:12:47 -0800 [thread overview]
Message-ID: <49419E6F.2000209@sgi.com> (raw)
In-Reply-To: <20081211225723.GD10890@mit.edu>
Theodore Tso wrote:
> On Thu, Dec 11, 2008 at 09:40:58AM +0100, Joerg Roedel wrote:
>> On Wed, Dec 10, 2008 at 05:04:39PM -0800, Linus Torvalds 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.
>>>
>> I'll vote for a. An open merge window over the holidays possible results
>> in needless stresses for the developers at a time which some of them
>> want to use otherwise. Or if any merge introduces bad bugs and the
>> developers that can fix it are on xmax vacation we may end up with an
>> unusable upstream tree for a week or so. Same with merge conflicts.
>> So, I'd suggest to wait until everybody is back to work until opening
>> the merge window.
>
> I'd vote for (a) as well, and hopefully folks who are really
> conscientious can do some integration testing of linux-next and can
> report problems there to make the merge window go more smoothly after
> the New Year's.
>
> - Ted
I'll second (or third?) this motion... ;-)
Thanks,
Mike
next prev parent reply other threads:[~2008-12-11 23:13 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 [this message]
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
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=49419E6F.2000209@sgi.com \
--to=travis@sgi.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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