[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1Ii1zU-0002Cj-EC@faramir.fjphome.nl>
Date: Wed, 17 Oct 2007 08:02:48 +0200
From: Frans Pop <elendil@...net.nl>
To: Pavel Roskin <proski@....org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Distinguishing releases from pre-rc snapshots
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
-
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