LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.28-rc1
Date: Thu, 23 Oct 2008 21:10:29 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0810232028500.3287@nehalem.linux-foundation.org> (raw)


It's been two weeks, so it's time to close the merge window. A 2.6.28-rc1 
is out there, and it's hopefully all good.

The changes in -rc1 are (as usual) too many to really enumerate, with the 
bulk of them being - again as usual - drivers. In fact, that's doubly true 
now that we merged the drivers from the staging tree. The dirstat output 
makes that very obvious:

   3.3% arch/arm/
  14.2% arch/
   3.1% crypto/
   4.0% drivers/media/
   3.7% drivers/net/wireless/
  10.3% drivers/net/
   6.5% drivers/staging/me4000/
   8.5% drivers/staging/slicoss/
   4.8% drivers/staging/wlan-ng/
  29.7% drivers/staging/
  63.6% drivers/
   3.3% include/
   4.6% net/
   4.6% sound/

but some other statistics may be fun: 

 - 7141 non-merge commits (and 419 merges)

 - average non-merge commit:
	39 lines removed, 104 lines added
   (not counting renames)

 - About 880 individual authors
	- 340 of which had just one commit
	- while 183 authors had ten or more commits

 - Most screwed-up clock award goes to:

	Greg Kroah-Hartman

   for his commit 51b90540, which claims to be from April 9 - six years 
   ago! And it's a fix to a driver that was merged this July!

Way to go, Greg!

Anyway, have fun, please test it, and report any intersting anomalies you 
find.

			Linus

             reply	other threads:[~2008-10-24  4:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24  4:10 Linus Torvalds [this message]
2008-10-24  4:14 ` Roland Dreier
2008-10-24 18:08   ` Greg KH
2008-10-24 11:24 ` Alistair John Strachan
2008-10-24 11:45   ` Rafael J. Wysocki
2008-10-24 12:52     ` Alistair John Strachan
2008-10-24 13:13       ` Alexey Dobriyan
2008-10-24 14:56         ` git-clean [Was: Linux 2.6.28-rc1] Björn Steinbrink
2008-10-24 15:17       ` Linux 2.6.28-rc1 Linus Torvalds
2008-10-24 19:22         ` Sam Ravnborg
2008-10-24 22:31         ` David Miller
2008-10-24 22:51           ` Sam Ravnborg
2008-10-24 19:15   ` Sam Ravnborg
2008-10-24 23:44     ` Alistair John Strachan
2008-10-24 17:09 ` Matt Mackall
2008-10-24 17:54   ` Matt Mackall
2008-10-24 17:57     ` Randy Dunlap
2008-10-24 18:05       ` Fenghua Yu
2008-10-24 18:11         ` Matt Mackall
2008-10-24 22:28 ` nf_conntrack oopes on parisc/smp (was Re: Linux 2.6.28-rc1) Domenico Andreoli
2008-10-24 22:53 ` Linux 2.6.28-rc1 Tony Vroon
2008-10-24 23:01   ` Arjan van de Ven
2008-10-26 13:17     ` Tony Vroon
2008-10-30 14:26 ` 2.6.28-rc1: NVRAM being corrupted on ppc64 preventing boot (bisected) Mel Gorman
2008-10-30 20:52   ` Paul Mackerras
2008-10-30 21:05     ` Josh Boyer
2008-10-30 21:35       ` Dave Kleikamp
2008-10-31 10:36     ` Mel Gorman
2008-10-31 11:10       ` Paul Mackerras
2008-10-31 11:31         ` Mel Gorman
2008-10-31 18:36         ` Mel Gorman
2008-10-31 11:18       ` Paul Mackerras
2008-10-31 11:31         ` Benjamin Herrenschmidt
2008-10-31 11:56           ` Paul Mackerras
2008-10-31 11:32         ` Mel Gorman
2008-10-24 18:10 Linux 2.6.28-rc1 Rufus & Azrael

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=alpine.LFD.2.00.0810232028500.3287@nehalem.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Linux 2.6.28-rc1' \
    /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

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).