linux-kernel - Re: [PATCH] Linux 3.8-merge version information

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFyFfjAnD4hR2SpE2OK8_dtHPkt0sr4BKZPhp6P7NKpiwQ@mail.gmail.com>
Date:	Tue, 11 Dec 2012 10:57:21 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Oliver Hartkopp <socketcan@...tkopp.net>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Linux 3.8-merge version information

On Tue, Dec 11, 2012 at 5:06 AM, Oliver Hartkopp <socketcan@...tkopp.net> wrote:
> As the automatically generated git version information is misleading in the
> merge window, name the kernel in the merge window as 3.8-merge .

This really doesn't help.

90% of the commits during the merge window wouldn't be based on that
Makefile change anyway, but on some much older version. So when
bisecting, for example, you'll see Makefiles with much older version
numbers, even though the commits got merged into the 3.8 merge window.

Also, we have code to generate the version number automatically. In
particular, I encourage people to use git trees and
CONFIG_LOCALVERSION_AUTO=y, because then your /var/log/messages (and
uname -r) will contain the exact git version of your kernel. So when
you see something like

    Linux version 3.7.0-rc8-00041-gcaf491916b1c

in your message log, you'll know that the kernel you were running back
then was 41 commits past -rc8, and had git commit ID of caf491916b1c.
And that is really useful for things like bisections ("Ok, I know it
worked three days ago - what kernel was I running then?") much more so
than a Makefile change would be (never mind how unreliable the version
info in the makefile is).

So this is why we only change the version in the Makefile when we do a
new tagged release.

                    Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/