Simon Large wrote:
> 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.
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.
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
> 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?
That's the problem. If you bring it back with the old name, you might
get a conflict with a new file with that name.
> 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.
Why do you want to have that old file back? And what do you want to do
with it? It's usually _not_ a good idea to update to an earlier
revision. Use the log dialog and choose "save as..." instead from that
> 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?
Sure. Updates to our docs are always welcome.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Aug 31 16:00:25 2004