From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Andrey Borzenkov <arvidjaar@mail.ru>,
linux-kernel@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Olaf Hering <olaf@aepfle.de>
Subject: Re: .version keeps being updated
Date: Wed, 10 Jan 2007 09:53:50 +0100 [thread overview]
Message-ID: <20070110095350.8669dbba.khali@linux-fr.org> (raw)
In-Reply-To: <20070109152534.ebfa5aa8.akpm@osdl.org>
Hi Linus, Andrew,
On Tue, 9 Jan 2007 15:25:34 -0800, Andrew Morton wrote:
> On Tue, 9 Jan 2007 15:21:51 -0800, Linus Torvalds wrote:
> > Actually, how about just removing the incrementing version count entirely?
>
> I use it pretty commonly to answer the question "did I remember to install
> that new kernel I just built before I rebooted"? By comparing `uname -a'
> with $TOPDIR/.version.
This will no longer work with the current state of things, as
$TOPDIR/.version keeps increasing.
> > (...) We have more useful _real_ versioning these days, with git commit
> > ID's etc.
These are completely different types of IDs. The .version number is a
local build ID and changes when one applies a local patch, or simply
changes a config option, and recompiles his/her kernel. The git ID of
course doesn't.
>From the other comments in this thread, it looks like the build ID is
something many people are interested in, so we can't just drop it.
--
Jean Delvare
next prev parent reply other threads:[~2007-01-10 8:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 9:20 .version keeps being updated Jean Delvare
2007-01-09 9:32 ` Gene Heskett
2007-01-09 17:05 ` Andrey Borzenkov
2007-01-09 20:44 ` Jean Delvare
2007-01-09 21:31 ` Andrew Morton
2007-01-09 23:21 ` Linus Torvalds
2007-01-09 23:25 ` Andrew Morton
2007-01-09 23:33 ` David Miller
2007-01-09 23:39 ` Andi Kleen
2007-01-10 1:43 ` Herbert Poetzl
2007-01-10 8:53 ` Jean Delvare [this message]
2007-01-10 16:52 ` Martin J. Bligh
2007-01-10 17:05 ` Jean Delvare
2007-01-10 11:31 ` Jan Engelhardt
2007-01-10 13:45 ` Roman Zippel
2007-01-10 16:01 ` Olaf Hering
2007-01-10 17:10 ` Jean Delvare
2007-01-10 19:02 ` Linus Torvalds
2007-01-10 19:31 ` Olaf Hering
2007-01-10 20:02 ` Olaf Hering
2007-01-10 22:56 ` Jan Engelhardt
2007-01-10 23:35 ` Segher Boessenkool
2007-01-11 13:27 ` Jan Engelhardt
2007-01-11 13:55 ` Andreas Schwab
2007-01-11 17:39 ` Segher Boessenkool
2007-01-11 18:01 ` Jan Engelhardt
2007-01-10 21:33 ` Linus Torvalds
2007-01-10 19:32 ` Linus Torvalds
2007-01-10 21:20 ` Andy Whitcroft
2007-01-11 10:56 ` Andy Whitcroft
2007-01-11 12:38 ` Roman Zippel
2007-01-11 13:05 ` Andy Whitcroft
2007-01-11 16:47 ` Linus Torvalds
2007-01-09 21:55 ` Luca Tettamanti
2007-01-10 7:34 ` Jean Delvare
2007-01-09 23:25 ` Willy Tarreau
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=20070110095350.8669dbba.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=arvidjaar@mail.ru \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=torvalds@osdl.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