[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Comparing CVS and SourceSafe (was RE: query)
From: |
Donald Sharp |
Subject: |
Re: Comparing CVS and SourceSafe (was RE: query) |
Date: |
Tue, 31 Jul 2001 16:52:31 -0400 |
User-agent: |
Mutt/1.2.4i |
On Tue, Jul 31, 2001 at 01:15:21PM -0700, Glew, Andy wrote:
> > I'd be carefull about saying that you can fix this. A corrupted ,v
> > generally not saveable. I've had plenty of times where
> > I know a ,v file is corrupted in one of the versions. There
> > is nothing I can do to retrieve that lost data. Yes good backups
> > are key but with cvs's mechanism of looking at data, corrupted
> > files can exist for a long time before you discover that it has
> > become corrupted. Months/Years can go by...
>
>
> Run something like this pseudo script as often as you like:
>
> FOR EACH file F in repository
> FOR EACH version V in its ,v file
> cvs co -rV F
> compute checksum, and compare to a saved checksum
>
> This checks that all versions you can extract are okay.
> You then need to verify that there are no missing versions
> - that's a bit more of a pain, since to do so totally transparent,
> in the presence of -o outdating, is more of a change.
> But if you never remove versions, having a checkin script
> or even the above scanner save the checksum suffices,
> and then you have a BOM.
>
>
> As in all things CVS, you need to roll this yourself.
>
I already got wrote this months ago ;). Check the archives
I've posted it..
donald