[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1006080214320.18052@chino.kir.corp.google.com>
Date: Tue, 8 Jun 2010 02:17:20 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Boaz Harrosh <bharrosh@...asas.com>
cc: Paul Mundt <lethal@...ux-sh.org>, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Frans Pop <elendil@...net.nl>,
Dirk Hohndel <hohndel@...radead.org>,
Len Brown <lenb@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH, v2] kbuild: Improve version string logic - two for the
price of one - No thanks
On Tue, 8 Jun 2010, Boaz Harrosh wrote:
> And you have broken the "localversion* semantics". Because my vanilla release
> is 2.6.rc2-my_tree-my_ver as checkedout and delivered from my official tree.
> Now you have added a "+" regardless of if it is an official tagged version or
> not.
>
The `+' modifies the base kernel version, not the version string.
Otherwise, it would be impossible to determine whether a "2.6.35-rc2-foo"
kernel were vanilla 2.6.35-rc2 or otherwise modified.
> I do not expect a complicated "let me be smarter than you" system that
> checks any tags of mine and provides an out-of-tree version system. I just
> want a switch that tells the system. "Let me shoot myself in the leg,
> I know what I want"
>
If you're using git, which you obviously are, then add localversion* files
to your repository (or modify CONFIG_LOCALVERSION if you pass along your
.config as well) and use git-tag to indicate its something you're
releasing as your kernel.
--
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/
Powered by blists - more mailing lists