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

[TSVN] Re: Rename in repository problem

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2004-08-31 14:24:48 CEST

"Simon Large" wrote
> There is a detailed explanation of why the wc works and the repo browser
> doesn't here:
> http://subversion.tigris.org/servlets/ReadMsg?list=users&msgNo=16865
>
> I am not sure if it is possible to fix the browser. Sounds like you need a
> command to use the HEAD revision of a file to find out what its URL was at
> rev N, and I am not clear whether this command exists except internally to
> SVN.

The SVN list seems to have gone quiet after your request for a consistent
interface ;-)
Seems to me that it is an essential piece of the API.

Even the simplest case of a single file rename seems broken at the moment.
Create repository and import files
In WC, rename one file and commit
In WC, update single file to pre-rename revision.
Oops! the file has disappeared from WC, but there is no error message.

If you update-to-rev the parent directory, it works OK and you get the old
file with its old name, as expected.

Bringing back a single renamed file is difficult anyway. Which name should
it have, old or new?

Both the SVN book and the TSVN guide say that renaming files and folders is
easy and safe. That much is quite true, but it does seem to make access to
old revisions more difficult.

I was thinking about writing a patch to give some more hints on choosing a
directory structure, because it is not always obvious when to have separate
repositories, or whether to use project/trunk or trunk/project. Does this
sound like a worthwhile update?

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 15:30: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.