From: Adrian Bunk <bunk@kernel.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what's with the "pre-releases" directory?
Date: Fri, 21 Mar 2008 19:56:51 +0200 [thread overview]
Message-ID: <20080321175651.GC1434@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <alpine.LFD.1.00.0803211336350.7227@localhost.localdomain>
On Fri, Mar 21, 2008 at 01:41:36PM -0400, Robert P. J. Day wrote:
> On Fri, 21 Mar 2008, Adrian Bunk wrote:
>
> > On Fri, Mar 21, 2008 at 01:13:45PM -0400, Robert P. J. Day wrote:
> > >
> > > just curious about this:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/v2.6/pre-releases
> >
> > These were the -test kernels that preceeded 2.6.0.
> >
> > > given that it seems filled with really old 2.6.0 content, what's the
> > > value in it? just curious.
> >
> > just curious about this:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/Historic
> >
> > given that it seems filled with really old content, what's the
> > value in it? just curious.
> >
> > ;-)
>
> um ... i'm going to assume you were being facetious since i can
> certainly see the value in the very, very first "official" release of
> linux, while still not seeing the point in a directory labelled
> "pre-releases" which contains nothing but pre-2.6.0 patches that go
> back to 2003. on the other hand, that *would* make sense under the
> Historic directory.
We even have
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/old-test-kernels/
The directory you spotted contains the pre-releases of 2.6 .
When is something historic and when might people search for it at the
old place?
But considering that one dir doesn't harm much I don't think there's
much point discussing it further.
> rday
>
> p.s. and while i'm whining, would it be possible to clear the
> obsolete "LATEST-IS" files out of:
>
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing
>
> i have a script that grabs the latest rc tarball out of that
> directory, and it got confused by seeing more than one LATEST-IS file.
> not hard to work around but, still ...
For this you have to whine to the guy who places them there:
-rw-rw-r-- 1 torvalds kernel 0 Mar 5 04:44 LATEST-IS-2.6.25-rc4
-rw-rw-r-- 1 torvalds kernel 0 Mar 10 05:30 LATEST-IS-2.6.25-rc5
-rw-rw-r-- 1 torvalds kernel 0 Mar 16 23:50 LATEST-IS-2.6.25-rc6
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-03-21 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 17:13 Robert P. J. Day
2008-03-21 17:34 ` Adrian Bunk
2008-03-21 17:41 ` Robert P. J. Day
2008-03-21 17:56 ` Adrian Bunk [this message]
2008-03-21 18:08 ` Robert P. J. Day
2008-03-21 21:16 ` Jan Engelhardt
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=20080321175651.GC1434@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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®