From: Jeff Garzik <jgarzik@pobox.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: sean <seandarcy2@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: BK snapshots removed from kernel.org?
Date: Wed, 30 Mar 2005 23:17:42 -0500 [thread overview]
Message-ID: <424B79E6.90300@pobox.com> (raw)
In-Reply-To: <424B72CC.8030801@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Randy.Dunlap wrote:
> sean wrote:
>
>> Randy.Dunlap wrote:
>>
>>>
>>> Did you look in
>>> http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/old/ ?
>>>
>>
>> Yes I did.
>>
>> Latest is 2.6.12-rc1-bk2, March 26.
>>
>> None since then?
>
>
> I can't explain it other than "the snapshots are broken."
> All I do is look around for them, and behold, just look in
>
> http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/
>
> for the 2.6.11.6-bk snapshots.
>
> It's confusing and it needs to be fixed....
>
> Jeff, is there some way that I can help to fix this,
> 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 ...
Jeff, still catching up from trip+engagement
[-- Attachment #2: get-version.pl --]
[-- Type: text/plain, Size: 710 bytes --]
#!/usr/bin/perl -w
use strict;
use Getopt::Std;
my (%opts, $mode, $s);
getopts('me', \%opts);
if ($opts{m}) {
$mode = 0;
} elsif ($opts{e}) {
$mode = 1;
} else {
die "usage: get-version.pl [-e | -m]\n";
}
$s = <>;
chomp $s;
my @line = split(/\./, $s);
my ($kmicro, $kextra);
if ($#line == 3) {
$kmicro = $line[2];
$kextra = "." . $line[3];
} else {
my @more = split(/-/, $line[2]);
if ($#more == 1) {
$kmicro = $more[0];
$kextra = "-" . $more[1];
} elsif (($#more == 0) && ($line[2] =~ /\d+/)) {
$kmicro = $more[0];
$kextra = "";
} else {
die "invalid extraversion parse";
}
}
if ($mode) {
$s = $kextra;
} else {
$s = $kmicro;
}
printf("%s\n", $s) unless ($s eq "");
exit(0);
[-- Attachment #3: snapshot.sh --]
[-- Type: application/x-sh, Size: 3723 bytes --]
next prev parent reply other threads:[~2005-03-31 4:19 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 [this message]
2005-03-31 4:29 ` Dave Jones
2005-03-31 4:44 ` Jeff Garzik
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=424B79E6.90300@pobox.com \
--to=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