Simon Large wrote:
>
> Sorry. I thought I had tried that, but evidently not. Checked it
> again and it works exactly as you say. It would be useful if the
> error message suggested the corrective action.
>
TSVN in HEAD already does give you a hint.
> If I had done the update correctly in the first place, then no, I
> would not need to do any of this. However, assuming I do rename the
> root folder in the repository for some reason, then update no longer
> works because it has lost its reference to the root folder, so I have
> to relocate.
That's true. If you rename the root folder then the working copy lost
its "anchor", and you must use the relocate command.
> If relocate is potentially dangerous, should there be a warning
> attached? Even better, can the program check that the URL is valid
> (assuming the database is online at the time)? The manual gives no
> indication that there may be problems here.
I proposed that to the subversion mailing list before. But they won't
add any more tests for URL validity. Sorry, couldn't convince them...
> I know the history is still there because I can see it in
> Repo-browser. I just tried the "Get All" button and it does indeed
> follow through the name change. Out of interest, why is this not the
> default behaviour?
Because people kept complaining. It _was_ the default behaviour, but
that wasn't what people wanted, since the "show log" is often used to
find out where a branch was created/started - and that's why the log
should stop on a copy.
> The "Get All" button does not appear to be documented in the helpfile
> or manual (as far as I can see), so I am still not sure exactly what
> it is doing - get all what?
The "show log" usually only shows the last 100 revisions. That's enough
for most use cases. It also stops on a copy (as of TSVN 1.0.7). The "Get
All" button then gets really _all_ log messages down to revision 1. You
can set the number of log messages the log dialog should show on the
first try in the settings dialog.
The reason for not fetching all log messages right away is that for big
repositories, this can take a while (try it on the subversion repository
for example: http://svn.collab.net/repos/svn).
Want to provide a patch for the docs?
> So would it be a good idea to add a warning dialog to repository
> folder rename? The data may be safe, but a mistake like this makes it
> very difficult/impossible to access (until 1.1.x arrives). I know
> renaming may be a stupid thing to do, but the point of having a nice
> front end like Tortoise is that it allows stupid people to use a
> revision control system.
The next TSVN will be from the 1.1.x branch of Subversion. So adding a
warning isn't necessary then anymore.
> Are you saying that in V1.1.x it will be safe to rename/relocate the
> root folder (even if it is un-necessary)?
No, not the root folder. But you can then safely rename every other
folder and still be able to do diffs/merges/tags/... on older revisions
where the target has a different name.
The root folder is somewhat special: it's like an anchor for the working
copy.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Aug 4 08:14:00 2004