From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: Linux 3.3-1 out - merge window closed
Date: Thu, 26 Jan 2012 01:48:36 -0800 [thread overview]
Message-ID: <20120126014836.aaf79457.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120120151452.2fe57bb87218f575e8909caf@canb.auug.org.au>
On Fri, 20 Jan 2012 15:14:52 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Thu, 19 Jan 2012 15:58:28 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
> >
> > (Stats for those that like them: 20% arch updates (arm, power, mips,
> > x86), 60% drivers (networking - wireless in particular, staging,
> > media, dri, sound, misc - including getting rid of 'struct sysdev'),
> > and 20% random stuff: filesystems, networking, perf etc)
>
> More stats for the bored:
>
> (I don't count merge commits below and everything is relative to v3.2)
>
> Of the 8899 commits in v3.3-rc1, 6918 were in next-20120106 (the first
> -next based on v3.2). A further 792 commits have the same subject line as
> commits in next-20120116 and a further 16 have the same patch-id.
>
> This leaves 1174 commits (13%) in v3.3-rc1 that were not in next-20120106
> for some reason (not too bad really, I guess).
That's a lot. Please name names!
I was impacted by several busted patches which had not appeared in
-next.
Also, I saw numerous patches which were significantly altered during
their trip from -next to mainline, which is cheating. These showed up
as a massive reject storm when I attempted to git-merge linus-now with
next-from-12-hours-ago. I went in and checked. tools/perf was a major
culprit.
> Some will clearly be bug
> fixes, of course. Some will be quilt trees (probably rebased before
> being sent to Linus). Some will be patches that depend on work by others.
The quilt trees would have been eliminated by the "commits have the
same subject line" test?
I don't think this is all a huuuge problem - we sort this stuff out
fairly quickly. But things could be improved a bit.
next prev parent reply other threads:[~2012-01-26 9:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 23:58 Linux 3.3-1 out - merge window closed Linus Torvalds
2012-01-20 4:14 ` Stephen Rothwell
2012-01-20 17:41 ` Steven Rostedt
2012-01-20 20:15 ` Junio C Hamano
2012-01-22 10:35 ` Geert Uytterhoeven
2012-01-26 9:48 ` Andrew Morton [this message]
2012-01-23 9:17 ` Ohad Ben-Cohen
2012-01-23 13:18 ` Grant Likely
2012-01-23 15:18 ` Arnd Bergmann
2012-01-24 0:32 ` Rusty Russell
2012-01-31 16:56 ` Paolo Bonzini
2012-02-01 2:49 ` Rusty Russell
2012-02-01 6:47 ` Ohad Ben-Cohen
2012-01-23 15:06 ` Carlos Chinea
2012-01-23 19:43 ` Linus Walleij
2012-01-24 18:57 ` Carlos Chinea
2012-01-25 11:35 ` Artem Bityutskiy
2012-01-25 11:47 ` Pekka Enberg
2012-01-25 12:06 ` Artem Bityutskiy
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=20120126014836.aaf79457.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 \
--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;
as well as URLs for NNTP newsgroup(s).