[Top] [All Lists]

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

To: Ethan Benson <erbenson@xxxxxxxxxx>
Subject: Re: plans for new release,update redate 2.4.18-5
From: Eric Sandeen <sandeen@xxxxxxx>
Date: 10 Jul 2002 14:40:47 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20020710113225.D32081@plato.local.lan>
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>
Sender: owner-linux-xfs@xxxxxxxxxxx
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... 
> also afaict the way the SGI version control system exports to CVS is
> to just deletes files which are moved/renamed or deleted, rather then
> moving them to a cvs attic, i may be wrong on this, it just appears so
> since whenever they remove/move/rename a file cvs just reports that
> `it no longer exists in the repository' instead of `is no longer
> pertenant'

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


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