[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Old repo backup, checkout current, lost repo, create new repo?

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 10 Dec 2018 22:56:17 +0100

On Mon, Dec 10, 2018 at 03:37:46PM -0600, Tom Browder wrote:
> On Mon, Dec 10, 2018 at 4:55 AM Tom Browder <tom.browder_at_gmail.com> wrote:
> >
> > On Mon, Dec 10, 2018 at 12:10 AM Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
> > > On Sun, Dec 9, 2018 at 6:31 PM Tom Browder <tom.browder_at_gmail.com> wrote:
> > ...
> > > > Given that history will be lost, does anyone see any problems with my recovery plan?
> > ...
> > > If you have working copies and you don't care about history, why are
> > > you spending any cycles on doing anything with hotcopy? You've lost
> > > history anyway, why keep any of it?
> ...
> > So, again, would my plan work to re-establish my repo and work flow?
> Ping? I really need some expert opinion here so I can proceed: is my
> plan to replace the lost repos with their hotcopies okay?
> Thanks.
> -Tom

Your current working copy will be invalidated if repositories are
back-dated. The SVN client will complain that it cannot find revisions
which are not present in the old hotcopy.

So if you use the old hotcopy, you need to check out a fresh working
copy and then move your current files from your current working copy
over to the fresh working copy, record any tree structure changes with
'svn add', 'svn remove', or 'svn move' as appropriate, and then commit
the result. This giant commit will then contain a combined version of all
the commits you have lost. Then you can continue working with SVN as usual.
Received on 2018-12-10 22:56:39 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.