From: Alexey Dobriyan <adobriyan@gmail.com>
To: Mark Hills <mark@pogo.org.uk>
Cc: linux-kernel@vger.kernel.org,
David Rientjes <rientjes@google.com>,
Michal Marek <mmarek@suse.cz>
Subject: Re: Appending '+' to version, since 2.6.35-rc2
Date: Mon, 14 Jun 2010 09:52:21 +0300 [thread overview]
Message-ID: <20100614065221.GB3999@x200> (raw)
In-Reply-To: <alpine.NEB.2.01.1006131729430.2991@jrf.vwaro.pbz>
On Sun, Jun 13, 2010 at 08:01:26PM +0100, Mark Hills wrote:
> Commit 85a256d adds a new feature:
>
> [...] When CONFIG_LOCALVERSION_AUTO is not enabled, a `+' is appended
> to the kernel version to represent that the kernel has been revised
> since the last release unless "make LOCALVERSION=" was used to uniquely
> identify the build.
>
> I'm finding this inconvenient for 'casual' kernel development.
>
> For example, my usual workflow goes something like:
>
> 1) find something I suspect is a bug
> 2) upgrade to the latest stable or -rc kernel, to confirm
> 3) experiment with patch to fix it
>
> Since 2.6.35-rc2, going from step 2 to 3 causes the version of the kernel
> to change: forcing time-consuming rebuilds,
init/version.c
kernel/configs.c
+ whatever patch has changed
+ vmlinux 2 or 3 times
That's not time consuming.
> installing modules, and manual
> changes associated with a new version number; eg. updating the lilo/grub
> config, or the distribution's initrd.
next prev parent reply other threads:[~2010-06-14 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 19:01 Mark Hills
2010-06-14 6:52 ` Alexey Dobriyan [this message]
2010-06-14 7:38 ` Mark Hills
2010-06-15 13:48 ` Benny Halevy
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=20100614065221.GB3999@x200 \
--to=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@pogo.org.uk \
--cc=mmarek@suse.cz \
--cc=rientjes@google.com \
/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®