[Top] [All Lists]

Re: plans for new release,update redate 2.4.18-5

To: linux-xfs@xxxxxxxxxxx
Subject: Re: plans for new release,update redate 2.4.18-5
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Wed, 10 Jul 2002 11:52:12 -0800
In-reply-to: <1026330047.27313.36.camel@stout.americas.sgi.com>; from sandeen@sgi.com on Wed, Jul 10, 2002 at 02:40:47PM -0500
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <3D2BFC15.574702F8@online.no> <3D2C1289.96B90856@hamburg.fcb.com> <20020710031549.C32081@plato.local.lan> <3D2C1C7C.AE277DD4@hamburg.fcb.com> <20020710113225.D32081@plato.local.lan> <1026330047.27313.36.camel@stout.americas.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Wed, Jul 10, 2002 at 02:40:47PM -0500, Eric Sandeen wrote:
> On Wed, 2002-07-10 at 14:32, Ethan Benson wrote:
> > that would be difficult since SGI does not actually use CVS, they use
> > a very interesting, but unspecific version control system that exports
> > to CVS, this means that there are no tags to efficiently let you
> > checkout an older version of the entire tree, you can inspect the
> > history of all the files whcih haven't been renamed/removed and see
> > every past revision but there is no way AFAIK to checkout a 2.4.18
> > version from CVS. (you can still get the patches from oss.sgi.com but
> > thats it).
> Well, you can look at the timestamps on the Makefile, to see when it
> bumped from 2.4.17 to 2.4.18, and then do a cvs checkout by date... 

doesn't really let you checkout the last 2.4.18 before it turned
2.4.19 where many many changes occured in between.. though its likly
even if you were using cvs that this would not have been tagged anyway.

> That's true; there is no such thing as an attic in our CVS repository. 
> :(  I agree that it's a pain.

given how crippled and broken cvs is im amazed that your exporter does
as well as it does.

Ethan Benson

Attachment: pgpd8XXtFoxtu.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>