mirror of https://lore.kernel.org/lkml/
 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.23-rc2
Date: Fri, 3 Aug 2007 20:50:43 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0708032031480.5037@woody.linux-foundation.org> (raw)


So I tried to hold people to the merge window, and said no to a few pull 
requests, but this whole "-rc2 is the new -rc1" thing is a disease, and 
not only is -rc2 late, it's bigger than it should be. Oh, well.

A lot of the changes are small, and a lot of them really are fixes, but 
there's a MIPS merge in there too, and some absolutely _huge_ diffs due to 
some drivers undergoing Lindent cleanups (28 _thousand_ lines changes in 
advansys.c, and the PNP files got Lindented too, although those weren't 
nearly as big).

But if you ignore the Lindent changes, the MIPS merge, the lguest 
documentation updates, and the MPT fusion driver changes, and the 
removal of the broken arm26 support, the rest of the changes really aren't 
that big.

But there's still a lot of those mostly small things all over. And the 
ShortLog is too large to post. But the full log along with the customary 
tar-balls and patches are out there on kernel.org. And as usual, the git 
tree gives you the goods if you just do

	git shortlog v2.6.23-rc1..

(the most interesting statistic from there is that we apparently had more 
than 250 people involved in just the -rc1 to -rc2 timeframe. Impressively 
spread out, in other words)

			Linus

             reply	other threads:[~2007-08-04  3:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04  3:50 Linus Torvalds [this message]
2007-08-04  4:14 ` david
2007-08-04  5:13 ` Jeff Chua
2007-08-04  5:34   ` Jeff Chua
2007-08-04 13:52     ` Jeff Chua
2007-08-04 16:11       ` Linus Torvalds
2007-08-04 18:06         ` H. Peter Anvin
2007-08-04 21:02           ` Antonino A. Daplas
2007-08-05  2:37           ` Jeff Chua
2007-08-05  3:11             ` H. Peter Anvin
2007-08-05 11:52               ` Jeff Chua
2007-08-07 17:05                 ` David Weinehall
2007-08-08  2:46                   ` Jeff Chua
2007-08-05  2:29         ` Jeff Chua
2007-08-05 12:04         ` Jeff Chua
2007-08-04 10:30 ` Rafael J. Wysocki
2007-08-04 22:15   ` Rafael J. Wysocki
2007-08-05  3:22 ` "Badness at kernel/irq/resend.c:70" on boot - via-pmu? Paul Collins
2007-08-05  4:41   ` Linus Torvalds
2007-08-05 21:51     ` Benjamin Herrenschmidt
2007-08-05 12:11 Linux 2.6.23-rc2 Jeff Chua
2007-08-05 12:40 ` Antonino A. Daplas
2007-08-05 13:26   ` Jeff Chua
2007-08-05 16:47     ` Rafael J. Wysocki
2007-08-06  0:36       ` Jeff Chua
2007-08-06 11:26         ` Rafael J. Wysocki
2007-08-06 12:34           ` Jeff Chua
2007-08-06 16:40           ` H. Peter Anvin
2007-08-06 15:40     ` Jan Engelhardt
2007-08-06 16:06       ` Jeff Chua
2007-08-06 16:34         ` Jan Engelhardt
2007-08-06 16:46         ` Indan Zupancic
2007-08-06 17:16           ` H. Peter Anvin
2007-08-06 17:32             ` Indan Zupancic
2007-08-06 17:33               ` H. Peter Anvin
2007-08-06 22:53                 ` Jeff Chua
2007-08-06 22:54                   ` H. Peter Anvin
2007-08-06 22:57                     ` Jeff Chua
2007-08-06 23:00                       ` H. Peter Anvin
2007-08-06 22:48           ` Jeff Chua
2007-08-06 23:20 Jeff Chua

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.0.999.0708032031480.5037@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®