[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs [annotate aborted]: invalid change text in <filename,v>

From: Todd Denniston
Subject: Re: cvs [annotate aborted]: invalid change text in <filename,v>
Date: Mon, 23 Sep 2002 13:20:14 -0500

Larry Jones wrote:
> Mike Ayers writes:
> >
> >       I have had problems on a few occasions recently with files getting
> > corrupted in my archive (oddest thing, really - I am only operating in
> > local mode on local drives, but I *am* running Windows...), which
> > have, fortunately, occured on rarely checked in files (the majority
> > citizen of most archives).  I fixed them by pulling an old archive,
> > verifying that the file was the same version as the corrupted file,
> > then verifying that they were different.  When I replaced the current
> > repository file with the archived one, all was once again hunky-dory.
> Corruption almost always occurs while updating the file, so it's
> exceedingly rare to have a correct, up-to-date backup for a corrupted
> file.  You've been exceedingly lucky (or unlucky, depending on your
> perspective).
> -Larry Jones
I am kind of curious here, have you (back up first) ran "scan disk" lately?
Ran low on drive space?
Or have your drives just had their out of warranty anniversary?

Not that I WANT to work in the windows environment, but if CVS/RCS as a
repository is unstable in a local mode there, I would like to know if it is
something CVS is doing or could protect against (besides refusing to work there

I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb.  Thank you.
        -- Vance Petree, Virginia Power

reply via email to

[Prev in Thread] Current Thread [Next in Thread]