mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Distinguishing releases from pre-rc snapshots
Date: Wed, 17 Oct 2007 08:02:48 +0200	[thread overview]
Message-ID: <E1Ii1zU-0002Cj-EC@faramir.fjphome.nl> (raw)
In-Reply-To: <1192587763.3672.24.camel@dv>

Pavel Roskin wrote:
> I'm trying to keep some external drivers up to date with the kernel, and
> the first two weeks after the release is the worst time for me.  There
> is no way to distinguish the current git kernel from the latest release.
> It's only after rc1 is released that I can use preprocessor to check
> LINUX_VERSION_CODE.
> 
> Before that, I have to rely on tricks or change the kernel version
> myself in a separate patch and tell other team members to do the same.
 
Note that you can see if there have been commits since a release (the last git tag) by using the command 'git describe'.

$ git checkout -b temp v2.6.23
Switched to a new branch "temp"
$ git describe
v2.6.23
$ git checkout master
$ git describe
v2.6.23-4223-g65a6ec0

Format is: last tag - # commits since last tag - id of HEAD commit

Hope this helps,
Frans Pop

  parent reply	other threads:[~2007-10-17  6:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  2:22 Pavel Roskin
2007-10-17  2:34 ` Dave Jones
2007-10-17  2:45   ` Pavel Roskin
2007-10-17  3:01     ` Dave Jones
2007-10-17  2:41 ` Rik van Riel
2007-10-17  3:17   ` Pavel Roskin
2007-10-17  6:02 ` Frans Pop [this message]
2007-10-17 12:59   ` Pavel Roskin

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=E1Ii1zU-0002Cj-EC@faramir.fjphome.nl \
    --to=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=proski@gnu.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®