From: Jeff Garzik <jgarzik@pobox.com>
To: Dave Jones <davej@redhat.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 23:44:53 -0500 [thread overview]
Message-ID: <424B8045.7040308@pobox.com> (raw)
In-Reply-To: <20050331042923.GB23124@redhat.com>
Dave Jones wrote:
> On Wed, Mar 30, 2005 at 11:17:42PM -0500, Jeff Garzik wrote:
> > >with the requirement (for me) that I not be required to use BK?
> > >I'll munge scripts or whatever...
> > >but I guess that I'll also need a kernel.org account to do that.
> >
> > Should hopefully just be changing get-version.pl ...
>
> hmm, it's going to go a bit nutso when it finds the most
> recent TAG: is from the bk pull of 2.6.11.x into Linus tree.
> So it generates -bk from /that/ instead of 2.6.12.
Correct (your description, not the code...), that is the problem that
causes snapshots to go bonkers.
> Could hack around it by checking the cset is from Linus I suppose ?
Probably best just to parse the Makefile, since TAG is no longer a valid
indicator.
> > Jeff, still catching up from trip+engagement
>
> Congrats!
Thanks!
Jeff
next prev parent reply other threads:[~2005-03-31 4:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 17:14 BK snapshots removed from kernel.org? 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 [this message]
2005-03-31 6:02 ` Greg KH
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=424B8045.7040308@pobox.com \
--to=jgarzik@pobox.com \
--cc=davej@redhat.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