[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4B75C8CB.DBDA.0014.0@hro.nl>
Date: Fri, 12 Feb 2010 21:31:58 +0100
From: "Sleddens, J.P.G." <j.p.g.sleddens@....nl>
To: "FTPAdmin Kernel.org" <ftpadmin@...nel.org>, <mirrors@...nel.org>,
<users@...nel.org>, "linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [kernel.org mirrors] [kernel.org users] XZ Migration
discussion
>>> On 12-2-2010 at 20:03, "H. Peter Anvin" <hpa@...or.com> wrote:
> On 02/12/2010 06:01 AM, Jean Delvare wrote:
>> 3* Create a new subdirectory for every 2.6.x kernel, and move all the
>> related files there. This would shrink the main index drastically, and
>> each subdirectory would have a reasonable size (except maybe 2.6.16 and
>> 2.6.27.) Oddly enough this has been done for the files under testing/
>> already, so I am curious why we don't do it for the release files (and
>> the testing/incr/ files, while we're at it.)
>
> Well, part of the reason why is that we're functionally "stuck" on 2.6;
> a prefix which really has lost all meaning.
>
> It might open up the question if we shouldn't just do a Solaris and drop
> the leading 2 (so the next kernel would be 6.33) or call the kernel
> after that 3.0 instead of 2.6.34, and then 3.1 instead of 2.6.35.
I remember the whole LKML discussion about this a few years back:
http://lkml.org/lkml/2008/10/15/377
The whole year.version or year/month versioning Greg HK proposed
made a lot of sense to me. It would also solve our problem with the 2.6
directory just growing and growing as the year versioning would make a
natural hierarchy which keeps going no matter what.
--
Jeffry Sleddens
Rotterdam University
--
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