From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 14
Date: Mon, 14 Jul 2008 10:12:42 -0700 [thread overview]
Message-ID: <20080714101242.ace33488.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080714201249.947400d0.sfr@canb.auug.org.au>
On Mon, 14 Jul 2008 20:12:49 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> With the opening of the merge window, I am hoping my job becomes easier
> again ... :-)
If past experience is a guide, it's about to get harder because
a) maintainers jam untested crap^W^Wrecently-received features into
their trees so they don't miss the merge window and
b) a storm of git rejects turn up as Linus's tree starts to get changed.
Hopefully b) will improve, as "all" the new code has already gone
through linux-next merging.
As for a), well, it would be nice if people were to be careful about
that sort of thing. In some ways it's justifiable - we _do_ have a
couple months to fix remaining glitches. But one would think that when
fast-tracking new features, the code would at least get additional
review and testing to make up for it.
next prev parent reply other threads:[~2008-07-14 17:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 10:12 linux-next: Tree for July 14 Stephen Rothwell
2008-07-14 11:43 ` Gabriel C
2008-07-14 13:47 ` Stephen Rothwell
2008-07-14 14:18 ` Gabriel C
2008-07-14 16:20 ` Takashi Iwai
2008-07-15 5:50 ` Benjamin Herrenschmidt
2008-07-14 16:20 ` Takashi Iwai
2008-07-14 16:25 ` Takashi Iwai
2008-07-14 16:25 ` Takashi Iwai
2008-07-14 17:12 ` Andrew Morton [this message]
2008-07-14 23:35 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2008-07-14 15:06 mkrufky
2009-07-14 7:06 Stephen Rothwell
2010-07-14 4:23 Stephen Rothwell
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=20080714101242.ace33488.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).