public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 3.10-rc4
Date: Sun, 2 Jun 2013 17:45:31 +0900 (PWT)	[thread overview]
Message-ID: <alpine.LFD.2.03.1306021745220.6129@pixel.linux-foundation.org> (raw)


Another week, another -rc. But this time (at least for now) only as a git 
tree - for people actually using the tar-balls and patches, I apologize, 
but I'm a complete moron, and didn't install kup, its perl dependencies, 
and my kup release scripts on the pixel before the trip.

And while I can read and write email, and git is fine with just a few 
(flaky) kB/s internet throughput I have access to right now, installing 
the perl packages etc seems to be a pipe dream.

I suspect nobody actually uses the tar-balls and patches, since git is so 
much more convenient and efficient, so hopefully nobody cares. But I'll 
rectify the lack eventually. Hopefully within a day or two, as my "yum 
update" actually completes. And if not in a day or two, then when I get 
back home a few days later.

Anyway, rc4 is smaller than rc3 (yay!).  But it could certainly be smaller 
still (boo!). There's the usual gaggle of driver fixes (drm, pinctrl, scsi 
target, fbdev, xen), but also filesystems (cifs, xfs, with small fixes to 
reiserfs and nfs).

And arch updates: m68k (mostly defconfig updates), powerpc, arm and x86.

Go forth and test.

                           Linus

             reply	other threads:[~2013-06-02  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02  8:45 Linus Torvalds [this message]
2013-06-02 18:39 ` Linux 3.10-rc4 Randy Dunlap
2013-06-03  9:09   ` Mikael Pettersson
2013-06-03  9:19     ` Linus Torvalds

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.03.1306021745220.6129@pixel.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