Messages in this thread | | | From | Linus Torvalds <> | Date | Tue, 11 Dec 2012 10:57:21 -0800 | Subject | Re: [PATCH] Linux 3.8-merge version information |
| |
On Tue, Dec 11, 2012 at 5:06 AM, Oliver Hartkopp <socketcan@hartkopp.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
| |