Lübbe Onken wrote:
> Stefan Küng wrote:
>> On 5/18/06, Lübbe Onken <l.onken@rac.de> wrote:
>>>
>>> The latest nightly still uses YES/NO. Wouldn't OK/CANCEL be the
>>> better choice?
>>
>> Not the way I changed the text. It's a YES/NO question now, so
>> OK/CANCEL would be 'wrong'. But of course, we can change the text to
>> something even better. Suggestions?
>
> By the way, we could change the text of the relocate warning, since
> it now only shows up when someone tries to shoot himself in the foot.
>
> I suggest something shorter than currently. Something like this:
>
> Caption: Relocate inside the same repository detected
> ------
> You are trying to _relocate_ your working copy _inside the same
> repository_ From %s [1] To %s [1] This is normally done by a _switch_
> operation.
>
> A relocate is only needed if the if the protocol or the server name
> or ip changes (e.g. http:// to https:// or http://svn.myserver.com/
> to http://svn.yourserver.com).
>
> An inadequately used relocate *will corrupt your working copy!* Now
> that you've read and hopefully understoiod the above:
>
> Do you really want to relocate?
>
> [Yes] [NO] [Help[2]]
> ------
>
> [1] Could you underline/highlight/different color the identical base
> URL in both lines? [2] Can you add a help button to the relocate
> warning?
>
> I left out all the conditions and ifnots that are IMHO confusing and
> tried to boil it down to the source of the problem.
If running locate inside the repo like this is so dnagerous why allow it?
TSVN could just pop up a warning syaing that it is a stupid thing to do and
if you really need to do it after all use the command line.
Bill
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else. In such case, you should destroy this
message and are asked to notify the sender by reply email.
Received on Thu May 18 12:03:17 2006