On 3/5/06, cleaner416 <cleaner416@mac.com> wrote:
> Recently the hard disk containing my code repositories crashed and I had to
> restore from a 1 week old backup. On a development machine I have made
> several changes to a couple of repositories and committed them during the
> week. So I still have the lastest code on my client machine, but the
> repository on the svn server is a week old. So now I have a situation like
> this:
>
> Development machine: has revision #45, doesn't think a commit is needed (I
> committed right before the server HD crash)
> Server that lost a week of commits has revision #40
>
> What's the best approach to re-sync here? I don't mind missing 41-44, but
> I'm hoping there is a solution where I can resync without simply blowing
> away the project and starting at rev 1 again with the latest source.
I think what I've seen recommended around here is to check out a fresh
WC from the repository (erv 40), then copy your changed files from the
old WC to the one you just created, then commit rev 41.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 8 17:55:53 2006