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

Re: new user need help (repo. older then working copy)

From: Kuang-Chun Cheng <kcc1967_at_gmail.com>
Date: 2007-12-11 20:30:24 CET

On Dec 12, 2007 2:48 AM, Ryan Schmidt <subversion-2007b@ryandesign.com>
wrote:

> On Dec 11, 2007, at 06:25, Kuang-Chun Cheng wrote:
>
> > On Dec 11, 2007 8:13 PM, Andy Levy wrote:
> >
> >> On Dec 11, 2007 6:55 AM, Kuang-Chun Cheng wrote:
> >>
> >> > My SVN repo. crash last week. I had re-install my RH5.1 and re-
> >> install
> >> > backup SVN repo. ....
> >> >
> >> > My project has up-to-date revison 4 in backup repo. But my
> >> working copy
> >> > already has revison 8.
> >> > I knew I will lost history of revision 5,6,7 .... that's OK.
> >> But how can
> >> > I re-commit my revison 8 into repository and make it revison 5
> >> in both
> >> > repo. and working copy ???
> >>
> >> Copy your changes to a safe place, check out a new working copy, copy
> >> your changes into that new WC, then commit.
> >
> > Any easier way to do that ?
> > Can I force working copy to old revision (rev 4 in my case)
> > without revert my modification ? Thanks a lot.
>
> Nope, no easier way. Do it the way Andy said.
>
> Subversion does not make this situation "easy" because it should
> never arise if you have up to date backups of your repository.
> Therefore, it is imperative that you have up to date backups of your
> repository at all times. Best practice: back up from the post-commit
> hook, after every commit.

Thanks .... and in fact, I already did that ...
However, I did believe the following feature should be useful (but it
doesn't work):
1) compare revision in repo. with a target directory (no matter it's a
working directory
   or not) and create a patch.
2) check out a new working copy
3) apply the patch to new working copy
4) commit patched version back to repo.

I think this is not a bad idea, so I tried it ... but it doesn't work :-(
Somehow, I feel subversion relies on working copy a little too much in my
case.
Anyway, I can live with that.

Use post-commit is OK ... but IMHO I won't say it's a great idea ....
because, basically, that
means subversion is "perfect" only if I always commit twice everytime.

Regards
KC
Received on Tue Dec 11 20:46:12 2007

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.