mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Linux 3.8-merge version information
Date: Sat, 15 Dec 2012 12:33:18 +0100	[thread overview]
Message-ID: <20121215113318.GA17019@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CA+55aFyFfjAnD4hR2SpE2OK8_dtHPkt0sr4BKZPhp6P7NKpiwQ@mail.gmail.com>

Hi!

On Tue 2012-12-11 10:57:21, Linus Torvalds wrote:
> 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.

Well, I'd say it helps in the common case.

> 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.

No, it does not solve bisect, but at least you get something
reasonable in the boot menu...?

> 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

Problem is that CONFIG_LOCALVERSION_AUTO adds a lot of time to
build. Like... making "empty" build twice as slow.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2012-12-15 11:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 13:06 Oliver Hartkopp
2012-12-11 18:57 ` Linus Torvalds
2012-12-11 19:33   ` Oliver Hartkopp
2012-12-15 11:33   ` Pavel Machek [this message]

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=20121215113318.GA17019@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=torvalds@linux-foundation.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®