RE: Repairing repository

[Bill]

Whatever you do, make sure you use tags liberally.  You should tag the whole
repository before you start and after you are done.  You should probably
also add tags in stages as you are going along.  It will pay off when you
find you committed something that was not merged properly.

-----Original Message-----
From: address@hidden [mailto:address@hidden Behalf Of
Eric Siegerman
Sent: Monday, July 29, 2002 15:38
To: address@hidden
Subject: Re: Repairing repository


On Mon, Jul 29, 2002 at 02:40:05PM -0400, Matt Riechers wrote:
> address@hidden wrote:
> >
> > I have copied the backup in to create a new repository.  Now I
> > must identify the files in the current working tree which are newer than
> > (different from) the files in the repository, and get them comitted.
Any
> > suggestions for the easy way to do this?
>
> What's wrong with 'cvs update/commit'?

Lots!  The sandbox's state information doesn't correspond with
the restored repo.  I don't know what the results will be, but it
could get ugly.

Look in the archives of this list for my message of July 4, 2002,
with the subject "cvs repository confusion".  That addresses a
slightly different situation, but you should be able to adapt it
to your needs.  If you have further questions, feel free to ask.

--

|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
        - Paul Schneider-Esleben

_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs