cleaner416 wrote:
> Greetings,
>
> 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.
Read the manuals at http://svnbook.red-bean.com/nightly/en/svn-book.html,
and the part about "General Vendor Branch Management Procedure". There's
also a tool available called svn_load_dirs.pl which that manual recommends.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 9 03:06:49 2006