From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, klive@cpushare.com,
Ian Wienand <ianw@gelato.unsw.edu.au>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: git tag in localversion
Date: Mon, 12 Sep 2005 16:31:24 -0500 [thread overview]
Message-ID: <d120d5000509121431765f52c8@mail.gmail.com> (raw)
In-Reply-To: <20050912210836.GL13439@opteron.random>
On 9/12/05, Andrea Arcangeli <andrea@suse.de> wrote:
> Hello,
>
> The patch that adds the git tag in the localversion is screwing klive a
> bit, see the 2.6.13-g* entries in
> http://klive.cpushare.com/?branch=unknown
>
> Those are supposed to go in the homepage but they're not recognized
> anymore due the git tag and so they go in the unknown page.
>
> So either we add a branch name in /proc/branch (for mainline that will
> be "2.6.13 mainline", that tells the release number and the branch, or I
> shall do a bit more of regexp on the localversion). The branch tag has
> the advantage of being able to more reliably recognize non-mainline
> kernels as well, klive was made for mainline, I didn't expect so many
> users with vendor kernels, but that's ok as long as the regexp on uname
> -r works ;). The regexp is already falling apart with distro like
> debian, so the sort of /proc/branch was suggested by them infact.
>
> Yet another way would be to remove the git tag from the localversion ;),
> but I doubt that it would be ok with you since it'd pratically backout
> the feature. I don't think it would be enough for you to have the git
> tag in /proc, the way I understand it you want it in the uts_release to
> avoid overwriting system.map.
>
> Suggestions welcome thanks.
I think this question better be addressed to Ian or Sam (Andrea, did
you pick a wrong entry from your address book?), adding them to CC...
--
Dmitry
next prev parent reply other threads:[~2005-09-12 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 21:08 git tag in localversion Andrea Arcangeli
2005-09-12 21:31 ` Dmitry Torokhov [this message]
2005-09-12 22:21 ` Andrea Arcangeli
2005-09-12 23:25 ` Dmitry Torokhov
2005-09-13 8:31 ` Ryan Anderson
2005-09-13 14:16 ` Andrea Arcangeli
2005-09-15 1:56 ` Andrea Arcangeli
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=d120d5000509121431765f52c8@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=andrea@suse.de \
--cc=dtor_core@ameritech.net \
--cc=ianw@gelato.unsw.edu.au \
--cc=klive@cpushare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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