Re: Option "--force": Misleading error message (II)

On Tue, 2003-12-16 at 05:43, Michael Schmitt wrote:
> here is another example where the comment on option "--force" is
> misleading.

It looks like the same example to me, just with a different filename.
Did I miss some subtle difference?

The --force message is not strictly wrong; it's just that there are two
restrictions involved, and only one can be forced. You can't move a
modified file without forcing, and you can't move a not-yet-committed
file at all.

It would certainly be better if we checked for the not-yet-committed
problem first (all not-yet-committed files are modified), but we're not
lying to you.

(A deeper problem here is that "--force" is specific to the command-line
client, and our libraries should not be generating error messages
specific to particular GUIs, much like web pages should not tell you to
press Ctrl-F to search for stuff within the page. But in both cases,
it's not immediately clear what should be done instead.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 16 17:08:02 2003