The device upon which my repository was stored has failed. I have last week's
backup, but I had done some checkins since then. Fortunately, I have an up to
date tree. I have copied the backup in to create a new repository. Now I
must identify the files in the current working
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Eric Siegerman
Sent: Monday, July 29, 2002 15:38
To: [EMAIL PROTECTED]
Subject: Re: Repairing repository
On Mon, Jul 29, 2002 at 02:40:05PM -0400, Matt Riechers wrote:
[EMAIL PROTECTED] wrote:
I have copied
On Tue, Jul 30, 2002 at 09:05:08AM -0400, Bill wrote:
Whatever you do, make sure you use tags liberally.
Emphatically seconded!
--
| | /\
|-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED]
| | /
Anyone who swims with the current will reach the big music steamship;
whoever
Okay, here's how I restored my repository from a recent archive of the
repository itself and a good working tree (sandbox). Thanks to all
who responded - I couldn't have done it without you.
First, all work is done on copies of the archive and the sandbox.
Whenever I made a
The device upon which my repository was stored has failed. I have last week's
backup, but I had done some checkins since then. Fortunately, I have an up to
date tree. I have copied the backup in to create a new repository. Now I
must identify the files in the current working tree
[EMAIL PROTECTED] 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
Matt Riechers wrote:
[EMAIL PROTECTED] 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
[EMAIL PROTECTED] wrote:
Will update then mark all files which
are different from the repository as commitable, so I can just commit
them and be back where I was? If so, my day just got considerably
brighter...
Essentially, yes. It will be as if you had checked out a fresh tree, and
just
If you have two different tree's( the cvs workspace and the hard copyout ).
I'd diff the two and then patch the changes into the cvs workspace...
donald
On Mon, Jul 29, 2002 at 11:48:53AM -0700, Mike Ayers wrote:
Matt Riechers wrote:
[EMAIL PROTECTED] wrote:
I have copied the backup
On Mon, Jul 29, 2002 at 02:40:05PM -0400, Matt Riechers wrote:
[EMAIL PROTECTED] 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
[EMAIL PROTECTED] wrote:
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.
Oops. You're right. If CVS/Entries has files dated newer than the
repository,
Matt Riechers wrote:
[EMAIL PROTECTED] wrote:
Will update then mark all files which
are different from the repository as commitable, so I can just commit
them and be back where I was? If so, my day just got considerably
brighter...
Essentially, yes. It will be as if you had
12 matches
Mail list logo
