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.35-rc1
Date: Sun, 30 May 2010 14:11:09 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.1005301356350.3986@i5.linux-foundation.org> (raw)


It's been two weeks, and so the merge window is closed. There may be a few 
trees I haven't pulled yet, but the bulk should all be there. And please, 
let's try to make the merge window mean something this time - don't send 
me any new pull request unless they are for real regressions or for major 
bugs, ok?

This time, there are no new filesystems (surprise surprise), but there's 
certainly been filesystem work both on an individual FS layer (btrfs, 
cept, cifs, ext4, nfs, ocfs2 and xfs) and at the VFS layer (superblock 
and quota cleanups in particular).

But as usual, the bulk of the changes are in drivers. About two thirds of 
all the changes, to be exact. infiniband, networking and staging drivers 
are the bulk of it, but there's changes all over (drm, sound, media, usb, 
input layer, you name it).

And what's good to see is that we continue to have very healthy 
statistics. About 8500 commits (of which 400+ are merges), with about a 
thousand individual developers involved (git counts 1047, but some of them 
are bound to be duplicates due to people mis-spelling their names etc). 
It's skewed, of course - with the median number of commits per person 
being just three - but I think that's what we want to see in a healthy 
development environment.

			Linus

             reply	other threads:[~2010-05-30 21:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-30 21:11 Linus Torvalds [this message]
2010-05-31  9:46 ` Jesper Nilsson
2010-06-01 15:51   ` Linus Torvalds
2010-05-30 21:25 Sedat Dilek

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.1005301356350.3986@i5.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®