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

[TSVN] Re: Re: Rename in repository problem

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-08-31 15:43:06 CEST

"Stefan Küng" wrote
> > In WC, update single file to pre-rename revision.
> ^^^^^^^^^^^^
> > Oops! the file has disappeared from WC, but there is no error message.
>
> What you did here isn't a good thing to do. If you update a single file
> to a different revision than the rest of your working copy, you'll get
> an inconsistent wc.

I agree, it is not a good thing to do. So should it be allowed at all for
single files?

> Now, for the file "disappearing":
> rev 1 testfile
> rev 2 rename testfile -> filetest
> now, if you update filetest to rev 1, it will disappear of course. Think
> about it: a rename is a delete followed by an add. So filetest was
> _added_ in revision 2 and therefore did not exist in revision 1.
> If you update the parent folder, then testfile will appear instead of
> filetest.

I can see the logic of this, but the behaviour is slightly inconconsistent.
I can diff the file through the namechange with no problem, so it is
intuitive (but wrong) to assume that an update-to-rev will replace the
current rev with the old one.

> Why do you want to have that old file back?

I don't really want it back - I am just trying to find problems on test data
so I don't get them on my real data.

> And what do you want to do with it? It's usually _not_
> a good idea to update to an earlier revision.

So what _would_ you use update-to-rev for?

> Use the log dialog and choose "save as..." instead from that earlier
revision.

Aha! That's another option I had not noticed.

Simon

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Aug 31 16:50:29 2004

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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