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.26-rc1
Date: Sat, 3 May 2008 12:38:20 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805031205330.2971@woody.linux-foundation.org> (raw)


So this merge window was somewhat rocky in the sense that there was a lot 
of arguments about it, but at the same time I at least personally think 
that from a technical angle, we had somewhat less scary stuff going on 
than has been almost the rule lately. 

Lots of changes, but nothing that really feels all that fragile to me. 
Famous last words. I expect that the x86 PAT support (which has been long 
in the making) has the potential to have some issues, but the obvious 
problems were hashed out long ago, and while the merge window already 
showed one bug, that one was fairly benign and quickly fixed.

As usual, the bulk of the changes are to drivers (roughly 40% of the 
diffs, and that's with rename detection - with renames shown as 
delete/create events it was pretty exactly half of the diff). The network 
driver updates were about half of that (again, that's not unusual, and is 
mostly indicative of the fact that there's a metric buttload of networking 
drivers out there).

Arch updates were another 20%, still leaving a fair amount of stuff spread 
out all over (that said, the "dirstat" with rename detection is a bit 
flaky - if files get renamed across directories, the accounting is 
obviously not very meaningful - so take the numbers as a guideline rather 
than anything else).

Among the randon stuff, filesystems (ext4, gfs2, ocfs2 and xfs stand out), 
and networking (with the generic 802.11 layer being a big part of it, so I 
guess that should counts as partly driver-related).

Of course, sometimes the small patches is what is more noticeable 
(especially if they introduce bugs ;). The VM doesn't really show up very 
big in diffstat, but there were a fair number of cleanups there.

Another feature that is notable not for its size, but because people have 
tried to get me to merge it for some long is kgdb support. Which really 
turned out pretty small and clean, once people started putting their 
effort into making it so.

So go out and test it. The diffstat and shortlogs are too big to post here 
(7500+ commits and the compressed full patch is 8.5MB in size), but one 
interesting tidbit I found was that during this *one* merge window, we had 
almost 800 different authors. Now, some of them will have gotten counted 
multiple times due to different versions of the same name, and I didn't 
filter that, but from a quick look, that is been pretty rare.

Obviously, most of those had just a couple of commits (more than half had 
three commits or less), but that's how everybody starts. 

			Linus

             reply	other threads:[~2008-05-03 19:39 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8287f540805041818g534c4e02qaadb0e749c5f3439@mail.gmail.com>
2008-05-03 19:38 ` Linus Torvalds [this message]
2008-05-03 21:47   ` Alistair John Strachan
2008-05-03 21:53     ` Alistair John Strachan
2008-05-04 12:30       ` Robin Holt
2008-05-04 13:56         ` Alistair John Strachan
2008-05-04 16:09           ` Robin Holt
2008-05-04 16:33             ` Alistair John Strachan
2008-05-05 21:04             ` Mauro Carvalho Chehab
2008-05-06  8:02               ` Alistair John Strachan
2008-05-06 10:31                 ` Mauro Carvalho Chehab
2008-05-06 14:34                   ` Stefan Richter
2008-05-06 14:54                     ` Stefan Richter
2008-05-06 19:13                     ` Mauro Carvalho Chehab
2008-05-06 19:44                       ` Stefan Richter
2008-05-06 20:06                         ` Mauro Carvalho Chehab
2008-05-06 20:47                           ` Stefan Richter
2008-05-06 22:39                             ` Mauro Carvalho Chehab
2008-05-06 23:36                               ` Stefan Richter
2008-05-08 12:48                                 ` Mauro Carvalho Chehab
2008-05-08 14:11                                   ` Stefan Richter
2008-05-06 23:48                             ` Stefan Richter
2008-05-04  7:29   ` [patch] sysfs: build fix Ingo Molnar
2008-05-04 18:40   ` Linux 2.6.26-rc1 Jan Engelhardt
2008-05-05  5:39   ` Andreas Mohr
2008-05-05  7:30     ` Ingo Molnar
2008-05-05 20:14       ` Mauro Carvalho Chehab
2008-05-06 13:07         ` Ingo Molnar
2008-05-07  8:35           ` Ingo Molnar
2008-05-05 23:51       ` Stephen Rothwell
2008-05-05 23:55         ` David Miller
2008-05-06  0:16           ` Andrew Morton
2008-05-06  5:57             ` Stephen Rothwell
2008-05-06  0:21           ` Ingo Molnar
2008-05-06  5:35           ` Stephen Rothwell
2008-05-06  6:56             ` David Miller
2008-05-06  7:26               ` Stephen Rothwell
2008-05-06  0:17         ` Ingo Molnar
2008-05-06  5:48           ` Stephen Rothwell
2008-05-06  6:07   ` Scheduling problems ? [ Was: Linux 2.6.26-rc1 ] J.A. Magallón
2008-05-06 13:11     ` Ingo Molnar

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.1.10.0805031205330.2971@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®