public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: dtor_core@ameritech.net
Cc: linux-kernel@vger.kernel.org, klive@cpushare.com
Subject: git tag in localversion
Date: Mon, 12 Sep 2005 23:08:36 +0200	[thread overview]
Message-ID: <20050912210836.GL13439@opteron.random> (raw)

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.

             reply	other threads:[~2005-09-12 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 21:08 Andrea Arcangeli [this message]
2005-09-12 21:31 ` git tag in localversion Dmitry Torokhov
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=20050912210836.GL13439@opteron.random \
    --to=andrea@suse.de \
    --cc=dtor_core@ameritech.net \
    --cc=klive@cpushare.com \
    --cc=linux-kernel@vger.kernel.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