Will Dean wrote:
> For me, "preview" means that I can see the _result_ before actually
> doing something (like print). But with a dry-run, you can't see what
> the result would be, you can only see which files _might_ get changed,
> not how they get changed.
>
> Yes, it's a lousy half-baked feature, so perhaps having a lousy
> half-baked name for it is actually appropriate.
>
>> So if you're not comfortable with a tooltip, we could extend the
>> label to
>> dry run (does not modify files)
>> instead. But I want to keep the term "dry run".
>
>
>
I found the term "dry run" conveyed the intended meaning perfectly,
albeit a little "dry" and am not compagning for any change there.
If there was sufficient impetus for change to get away from the
uniqueness then maybe "trial merge", just as in accounting practice we
have "trial balance" .
What I would like to see though is it implemented as a separate button
to launch the trial merge rather than a persistant checkbox.
On a number of occasions after doing a successful "dry run" on a big
merge I have gone to do the real merge and later discovered that nothing
happened.
My fault for being inatentive and not noticing that little x-in-a-box
down there in the corner but anything to help speed the process would be
really appreciated.
I know, make it customer configuarble! (then wait for the inevitible "I
clicked on the "see if it works" checkbox and now all my merges fail)
Peter McNab
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jan 20 01:12:51 2005