From: Linus Torvalds <torvalds@osdl.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 2.6.13-rc1
Date: Tue, 28 Jun 2005 23:30:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0506282310040.14331@ppc970.osdl.org> (raw)
Ok, guys,
there was a lot of stuff pending after 2.6.12, and in the week and a half
since the release, the current diff against it has grown to almost three
megabytes compressed.
Which is actually normal for a -rc1 release judging by the two last ones,
but it usually takes us longer than ten days to get there. Which just
shows that 2.6.12 was brewing for too long, but we can also think
positively and say that perhaps it also seems to imply that this git thing
is working out and not slowing people down.
Anyway, I really don't want to drag out 2.6.13 as long as 2.6.12 took, and
we don't have any reason to anyway, so let's try to see if we can calm
things down again, and people who are thinking about writing new code
might think about spending some quality time looking at the existing code
and patches instead.
Now, that big patch ends up being spread out over 2069 commits, and a
noticeable chunk of it is actually the new xtensa architecture that got
merged, but that still leaves a lot of patches all over the place (things
like a few new console fonts, for example ;). The shortlog is over 100kB
in size, which means that I think linux-kernel won't take it if I include
it here, so I won't. Similarly, the diffstat is 200kB, partly because of
the spread out nature of the pacthes.
ARM, x86[-64], ppc, sparc updates, networking, sound, infiniband, input
layer, ISDN, MD, DVB, V4L, network drivers, pcmcia, isofs, jfs, nfs,
xfs, knfsd.. You name it.
Git trees and traditional patches/tar-balls are out there, or at least
slowly mirroring out. Go wild,
Linus
next reply other threads:[~2005-06-29 6:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 6:30 Linus Torvalds [this message]
2005-06-29 7:46 ` Brice Goglin
2005-06-29 9:02 ` Brice Goglin
2005-06-29 9:29 ` William Lee Irwin III
2005-06-29 12:13 ` Linux 2.6.13-rc1 - [PATCH] Don't fill up log with atxp1 vcore change message Prakash Punnoor
2005-06-29 15:01 ` Linux 2.6.13-rc1 - bad tag in git tree? Dave Kleikamp
2005-06-29 15:28 ` Jeff Garzik
2005-06-29 15:45 ` Linus Torvalds
2005-06-29 19:31 ` Linux 2.6.13-rc1 Jesper Juhl
2005-06-29 21:00 ` David Weinehall
2005-06-29 22:34 ` Bill Davidsen
[not found] <4kEoS-Am-3@gated-at.bofh.it>
2005-06-29 14:23 ` Ronny V. Vindenes
2005-06-29 14:58 ` Tomasz Torcz
2005-06-29 15:07 ` Hugh Dickins
2005-06-29 15:20 ` Ronny V. Vindenes
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=Pine.LNX.4.58.0506282310040.14331@ppc970.osdl.org \
--to=torvalds@osdl.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®