Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20201214 was the first linux-next after
the merge window opened.)
Commits in v5.11-rc1 (relative to v5.10): 12498
Commits in next-20201214:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20201009 was the first linux-next after
the merge window opened.)
Commits in v5.10-rc1 (relative to v5.9): 13903
Commits in next-20201009:
Hi all,
On Sun, 14 Jun 2020 13:44:07 -0700 Linus Torvalds
wrote:
>
> So I didn't really expect this, but 5.8 looks to be one of our biggest
> releases of all time.
This was the second largest linux-next (and may have been the largest
if June 1 had not been a pubic holiday here).
As usual, the
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20190709 was the first linux-next after
the merge window opened.)
Commits in v5.3-rc1 (relative to v5.2):12608
Commits in next-20190709:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20190507 was the first linux-next after
the merge window opened.)
Commits in v5.2-rc1 (relative to v5.1):12064
Commits in next-20190507:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20190304 was the first linux-next after
the merge window opened.)
Commits in v5.1-rc1 (relative to v5.0):11241
Commits in next-20190304:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20181224 was the last linux-next before
the merge window opened.)
Commits in v5.0-rc1 (relative to v4.20): 10843
Commits in next-20181224:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20181019 was the last linux-next before
the merge window opened.)
Commits in v4.20-rc1 (relative to v4.19): 12125
Commits in next-20181019:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180813 was the first linux-next after
the merge window opened.)
Commits in v4.19-rc1 (relative to v4.18): 12317
Commits in next-20180813:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180604 was the first linux-next after
the merge window opened.)
Commits in v4.18-rc1 (relative to v4.17): 11594
Commits in next-20180604:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20170704 was the first linux-next after
the merge window opened.)
Commits in v4.13-rc1 (relative to v4.12): 11258
Commits in next-20170704:
Hi Stephen,
On Tue, May 16, 2017 at 07:32:09AM +1000, Stephen Rothwell wrote:
> On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote:
> > On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote:
> > > There are also 288 commits in next-20170502 that didn't make it into
> > > v4.12-
Hi Sebastian,
On Mon, 15 May 2017 16:51:08 +0200 Sebastian Reichel wrote:
>
> On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote:
> > There are also 288 commits in next-20170502 that didn't make it into
> > v4.12-rc1.
> >
> > [...]
> >
> > Top ten commiters:
> >
> > 66 s...@c
Hi,
On Mon, May 15, 2017 at 11:15:50PM +1000, Stephen Rothwell wrote:
> There are also 288 commits in next-20170502 that didn't make it into
> v4.12-rc1.
>
> [...]
>
> Top ten commiters:
>
> 66 s...@canb.auug.org.au
> 47 paul...@linux.vnet.ibm.com
> 34 t...@linutronix.de
> 23
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20170502 was the first linux-next after
the merge window opened.)
Commits in v4.12-rc1 (relative to v4.11): 12920
Commits in next-20170502:
Hi,
On Mon, Mar 06, 2017 at 10:52:00AM +1100, Stephen Rothwell wrote:
> > - a couple of subsystems. drm, Infiniband, watchdog and btrfs stand out.
> Top ten first word of commit summary:
...
> 61 btrfs
I can comment on the btrfs part. We have lots of cleanups for 4.11 and
good part of all
Hi Linus,
On Sun, 5 Mar 2017 13:41:04 -0800 Linus Torvalds
wrote:
>
> It _does_ feel like there was more stuff that I was asked to pull than
> was in linux-next. That always happens, but seems to have happened
> more now than usually. Comparing to the linux-next tree at the time of
> the 4.10 re
Hi All,
On Sun, 25 Dec 2016 16:41:46 -0800 Linus Torvalds
wrote:
>
> It's Christmas Day, and it's two weeks since the merge window opened.
> Thus, the merge window is now closed.
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted,
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20161004 was the first linux-next after
the merge window opened.)
Commits in v4.9-rc1 (relative to v4.8):14308
Commits in next-20161004:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20160725 was the first linux-next after
the merge window opened.)
Commits in v4.8-rc1 (relative to v4.7):11618
Commits in next-20160725:
Hi all,
I have been a bit remiss in publishing these stats and maybe that has
lead to the current lower result for commits in linux-next before the
merge window opened ...
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-201
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20151103 was the first linux-next after
the merge window opened.)
Commits in v4.4-rc1 (relative to v4.3):11528
Commits in next-20151103:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20150831 was the first linux-next after
the merge window opened.)
Commits in v4.3-rc1 (relative to v4.2):10756
Commits in next-20150831:
Hi all,
[These will be easier in the future as I have now scripted this message]
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20150623 was the first linux-next after
the merge window opened.)
Commits in v4.2-rc1 (relati
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20140804 was the first linux-next after
the merge window opened.)
Commits in v3.17-rc1 (relative to v3.16): 10872 (v3.16-rc1: 11364)
Commits in next-201408
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20140602 was the first linux-next after
the merge window opened.)
Commits in v3.16-rc1 (relative to v3.15): 11364 (v3.15-rc1: 12034)
Commits in next-20140602:
On Fri, 22 Nov 2013 12:36:37 -0800 Linus Torvalds
wrote:
>
> Talking about mistakes... I suspect it was a mistake to have that
> extra week before the merge window opened, and I probably should just
> have done a 3.12-rc8 instead. Because the linux-next statistics look
> suspicious, and we had ex
On Tue, Sep 17, 2013 at 03:50:57PM +1000, Stephen Rothwell wrote:
> 21 Sachin Kamat
These should all be fixes, Sachin submitted a bunch of fixes for common
patterns with errors just about the time the merge window opened.
signature.asc
Description: Digital signature
Stephen,
On Tue, Sep 17, 2013 at 03:50:57PM +1000, Stephen Rothwell wrote:
> There are also 358 commits in next-20130701 that didn't make it into
> v3.11-rc1.
>
> Top ten first word of commit summary:
>
> 56 arm
>
> Top ten authors:
>
> 13 Sebastian Hesselbarth
>
> Top ten commite
On Wed, Sep 18, 2013 at 2:37 AM, Stephen Rothwell wrote:
>> > So better than last time, but it would be still nice to figure out where
>> > the last lot came from. I have the "git log --oneline --no-walk" list if
>> > someone wants them.
>> >
>> > Some breakdown of that list:
>> I'm totally conf
Hi Nicholas,
On Tue, 17 Sep 2013 17:23:41 -0700 "Nicholas A. Bellinger"
wrote:
>
> On Tue, 2013-09-17 at 15:50 +1000, Stephen Rothwell wrote:
> > On Mon, 16 Sep 2013 18:08:11 -0400 Linus Torvalds
> > wrote:
> > >
> > > So it's been two weeks, and the merge window for 3.12 is now closed.
> >
>
Hi Stephen,
On Tue, 2013-09-17 at 15:50 +1000, Stephen Rothwell wrote:
> On Mon, 16 Sep 2013 18:08:11 -0400 Linus Torvalds
> wrote:
> >
> > So it's been two weeks, and the merge window for 3.12 is now closed.
>
> As usual, the executive friendly graph is at
> http://neuling.org/linux-next-size.
Hi Stephen,
I am subscribed to linux-next but I did not receive [1].
If you did not CC linux-next, can you do this next time?
Thanks.
Your stats have a lot of number, I am not sure if I read/interpret
them correctly.
Just one number is interesting for me:
How many commits/patches were taken from
On Mon, 16 Sep 2013 18:08:11 -0400 Linus Torvalds
wrote:
>
> So it's been two weeks, and the merge window for 3.12 is now closed.
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20130903 was the linux-next based on v3.11)
On Mon, 2013-05-13 at 11:18 +1000, Stephen Rothwell wrote:
> 47 powerpc
Oops ;-)
So most of that *was* in -next for at least a day or two afaik just not
before the merge window opened. The reason for that is that I was on
an extended vacation for 5 weeks and was playing catch up until fairly
On Sat, 11 May 2013 18:00:09 -0700 Linus Torvalds
wrote:
>
> So this is the biggest -rc1 in the last several years (perhaps ever)
ever (see http://neuling.org/linux-next-size.html after today's
linux-next release).
> Which was unexpected, because while linux-next was fairly big, it
> wasn't exc
Hi all,
On Mon, 4 Mar 2013 15:22:22 +1100 Stephen Rothwell
wrote:
>
> So commits in -rc1 that were "in" next-20130220: 930090.6%
> (down from 90.0% last time)
That should read "down from 90.9% last time".
At least I know that one person re
On Sun, 3 Mar 2013 16:28:25 -0800 Linus Torvalds
wrote:
>
> It's been two weeks (ok, thirteen days, but close enough), and the
> merge window is closed, and I've cut the 3.9-rc1 release.
>
> I don't know if it's just me, but this merge window had more "Uhhuh"
> moments than I'm used to. I stoppe
On Fri, 21 Dec 2012 18:00:58 -0800 Linus Torvalds
wrote:
>
> The longest night of the year is upon us (*), and what better thing to
> do than get yourself some nice mulled wine, sit back, relax, and play
> with the most recent rc kernel?
>
> This has been a big merge window: we've got more commi
Hi all,
Well here are this merge windows' stats:
(No merge commits counted, next-20121001 is the first linux-next after
v3.6)
Commits in v3.7-rc1 (relative to v3.5): 10409
Commits in next-20121001: 10459
Commits with the same SHA1: 8068
Commits with the same patch_id:
Hi all,
Well here are this merge windows' stats:
(No merge commits counted, next-20120722 is the first linux-next after
v3.5)
Commits in v3.6-rc1 (relative to v3.5): 8587
Commits in next-20120521: 9245
Commits with the same SHA1: 6711
Commits with the same patch_id:
41 matches
Mail list logo
