From: Greg KH <greg@kroah.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>, sean <seandarcy2@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: BK snapshots removed from kernel.org?
Date: Wed, 30 Mar 2005 22:02:01 -0800 [thread overview]
Message-ID: <20050331060201.GB25365@kroah.com> (raw)
In-Reply-To: <424B79E6.90300@pobox.com>
On Wed, Mar 30, 2005 at 11:17:42PM -0500, Jeff Garzik wrote:
>
> Should hopefully just be changing get-version.pl ...
Nah, this simple patch to snapshot fixes it.
I've also generated the 2.6.12-rc1-bk3 snapshot and fixed up the
directory on kernel.org so it should now work properly if you apply the
patch.
Sorry about this issue, I never thought that tags in the bk tree would
cause such a mess...
thanks,
greg k-h
--------------
--- snapshot.orig 2005-03-30 21:44:16.869023655 -0800
+++ snapshot 2005-03-30 21:45:30.410153125 -0800
@@ -39,9 +39,12 @@
#
# discover most recent kernel version
#
-tmptagver=`bk changes | grep 'TAG: v' | head -1 | awk '{print $2}'`
-kmicro=`echo $tmptagver | $getver -m`
-kextra=`echo $tmptagver | $getver -e`
+bk get -q Makefile
+for TAG in SUBLEVEL EXTRAVERSION ; do
+ eval `sed -ne "/^$TAG/s/ //gp" Makefile`
+done
+kmicro="$SUBLEVEL"
+kextra="$EXTRAVERSION"
kversion="$kmajor.$kminor.$kmicro$kextra"
snapdir="$snapbase" # /$kversion
echo "found kernel version $kversion" >> $log
next prev parent reply other threads:[~2005-03-31 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 17:14 Norberto Bensa
2005-03-27 21:02 ` Barry K. Nathan
2005-03-28 15:26 ` Norberto Bensa
2005-03-28 15:40 ` Randy.Dunlap
2005-03-28 17:19 ` Norberto Bensa
2005-03-31 3:34 ` sean
2005-03-31 3:47 ` Randy.Dunlap
2005-03-31 3:58 ` Dave Jones
2005-03-31 4:17 ` Jeff Garzik
2005-03-31 4:29 ` Dave Jones
2005-03-31 4:44 ` Jeff Garzik
2005-03-31 6:02 ` Greg KH [this message]
2005-03-31 11:42 ` Prakash Punnoor
2005-03-31 20:25 ` Greg KH
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=20050331060201.GB25365@kroah.com \
--to=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=seandarcy2@gmail.com \
/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®