Ryan Schmidt wrote:
>
> On Jan 10, 2008, at 15:33, Matthew Trost wrote:
>
>> I was able to reload the repository from the latest dump file, and it
>> put the revision at 1. I guess this is fine.
>
> Are you sure this is fine? You'll lose all past log messages, all past
> history and the ability to recover anything you svn rm'd, you'll have
> to check out new working copies, any references to the old revision
> numbers for example in your issue tracker will now be invalid, etc.
>
>> I'm going to verify that everything is there that should be. Thanks
>> for your help.
>
>
>
I'd prefer to retain the history, but I don't know of another way to
reload successfully.
My initial approach was to copy the backed up repository back to its
rightful place. This put the repository at revision 306, and it works
perfectly except that it's 10 revisions behind where the "live" code
is. Since I don't actually have the incremental revision dump files to
get me there, I had to start over. What I did was blow away the
repository, and create it anew in the same directory. Then I went to
the command line and did the svnadmin load command using the most recent
dump file. Is there another way that you know of?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-10 22:53:46 CET