Linux Kernel 2.6.12

2.6.12 (2005.06.18)

As some people may have noticed already, 2.6.12 is out there now. The full ChangeLog ended up missing, because I only have the history from 2.6.12-rc2 in my git archives, but if you want to, you can puzzle it together by taking the 2.6.12 changelog and merging it with the -rc1 and -rc2 logs in the testing directory. The file that says "ChangeLog-2.6.12" only contains the stuff from -rc2 onward. Included here in the email are the changes since -rc6, and as you can see from the appended diffstat, most of the things are pretty small (ie it looks like a long list, and then you look at the diffstat and realize that most of the changes end up being just a line or two). One of the least important changes is still worth pointing out: it was discussed earlier on the kernel mailing list in another thread, but maybe people didn't notice it: the sign-off procedure was clarified to make it clear that the person signing off understands that the project - and thus the patch and the sign-off itself, of course - is public and will be archived. This may sound silly and obvious - and it is - but it makes people more comfortable about the fact that we obviously save identifying information in the sign-off (that's the whole point), and in general people also submit things like their own email addresses in CREDITS files etc, and so nobody should be expecting any of that to be kept confidential. I don't think anybody did, of course, but hey, this way it's explicit. So part of the new stuff is this patch:
        diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
        --- a/Documentation/SubmittingPatches
        +++ b/Documentation/SubmittingPatches
        @@ -271,7 +271,7 @@ patch, which certifies that you wrote it
         pass it on as a open-source patch.  The rules are pretty simple: if you
         can certify the below:

        -        Developer's Certificate of Origin 1.0
        +        Developer's Certificate of Origin 1.1

                 By making a contribution to this project, I certify that:

        @@ -291,6 +291,12 @@ can certify the below:
                     person who certified (a), (b) or (c) and I have not modified

        +       (d) I understand and agree that this project and the contribution
        +           are public and that a record of the contribution (including all
        +           personal information I submit with it, including my sign-off) is
        +           maintained indefinitely and may be redistributed consistent with
        +           this project or the open source license(s) involved.
         then you just add a line saying

                Signed-off-by: Random J Developer 
just so that people are aware of this. Btw, in case anybody ends up wondering about what the actual patches are, if you're a git user (or, more likely, not quite a user yet, but rather wondering what you can do with git), you can start off with doing git-whatchanged -p v2.6.12-rc6..v2.6.12 and it will do exactly what you think it migth do - it shows every commit between -rc6 and the final 2.6.12 release as a patch ("-p") with the associated commit message. Linus

2.6.12-rc6 (2005.06.06)

It's being uploaded right now, the git tree is already up-to-date, and by the time this hits the mailing list the mirroring of the tar-ball will hopefully be done too. And since Jeff wrote me a shortlog script for git, the easist way to tell what's new since -rc5 is to just do the shortlog and diffstat output. Network drivers, USB and CPU-freq stand out. And the good news is that people do seem to have taken my rumblings about calming down for 2.6.12 seriously. Let's hope that pans out, and I can release that one asap.. But give this a good beating first, and holler (again, if you must) about any issues you have, Linus

2.6.12-rc5 (2005.05.24)


2.6.12-rc4 (2005.05.07)

You know the drill. git trees, patches, tar-balls, you name it. I've still not made a shortlog script, and right now I'm too tired to generate the shortlog from the full log, so you can either find it all in the git archives, or just parse down the full log in ChangeLog-2.6.12-rc4 to a more manageable format. Both the full log and the diffstat are too big for the mailing list to accept, so I'll not spam your mailboxes. But you could just use gitweb, in case you haven't noticed already. So point your browsers at and see what you find out that way. What's changed? ia64, arm, UML, ppc64, jfs, cifs updates. And drivers. And tons of small stuff all over. Me, I'm off for a week of vacationing. Flee the country, like I usually do after releases. Leave you suckers^H^H^H^H^H^H^Hgentle people to test it all out. Linus

2.6.12-rc3 (2005.04.20)

Ok, you know what the subject line means by now, but this release is a bit different from the usual ones, for obvious reasons. It's the first in a _long_ time that I've done without using BK, and it's the first one ever that has been built up completely with "git". It's available both as a patch (against 2.6.11) and as a tar-ball, and for non-BK users the biggest difference is probably that the ChangeLog format has changed a bit. And it will probably continue to evolve, since I don't have my "release-script" tools set up for the new setup, so this release was done largely manually with some ad-hoc scripting to get the ChangeLog information etc out of git. For BK users, I hope we can get a BK tree that tracks this set up soon, and it should hopefully not be too disruptive either. And for the crazy people, the git archive on is up and running under /pub/scm/linux/kernel/git/torvalds/linux-2.6.git. For the adventurous of you, the name of the 2.6.12-rc3 release is a very nice and readable: a2755a80f40e5794ddc20e00f781af9d6320fafb and eventually I'll try to make sure that I actually accompany all releases with the SHA1 git name of the release signed with a digital signature. One of the tools I don't have set up yet is the old "shortlog" script, so I did this really hacky conversion. You don't want to know, but let's say that I'm re-aquainting myself with 'sed' after a long time ;). But if some lines look like they got hacked up in the middle, rest assured that that's exactly what happened, and the long log should have the rest ... Linus

2.6.12-rc2 (2005.04.05)

The diffstat output tells the story: this is a lot of very small changes, ie tons of small cleanups and bug fixes. With a few new drivers thrown in for good measure. This is also the point where I ask people to calm down, and not send me anything but clear bug-fixes etc. We're definitely well into -rc land. So keep it quiet out there, Linus

2.6.12-rc1 (2005.03.18)


2.6.11; 2.6.12 API Changes

Archived comments:

DoomHammer 2005-06-18 14:01:05

lubisz puzzle? :D

zdzichuBG 2005-06-18 14:04:11

Tak, głównie takie z morskimi widoczkami ;)


Comments powered by Disqus