Barry Scott wrote:
> On Mar 12, 2006, at 14:29, Vincent Starre wrote:
>> Julian Foad wrote:
>>> Vincent Starre wrote:
>>>> Simple request here. Sometimes SVN says something like "cannot do
>>>> this, file has local changes. (use --force to override this
>>>> restriction)", but it doesnt do anything to explain the true
>>>> implications of this. I am left wondering when, for example, I
>>>> move a modified file, "Does this mean it will destroy my changes?"
>>>> Anyone agree/disagree?
>>> I agree. The right place to explain what "--force" does is in the
>>> help (not in the error message). The help system has recently been
>>> modified to allow the description of an option to be tailored to
>>> suit different subcommands.
>> I would disagree with that. The help has no way of being entirely
>> specific to your own situation. For example: --force might cause the
>> over-writing of a file which exists, /or/ it might cause
>> partially-missing history (or both). Being told all the things --
>> force might do would be just as ambiguous as guessing all the things
>> --force might do, wouldnt it?
> The third way might be to list what would happen when a dry run is
> performed with --force --dry-run.
The trouble is, how much would be "listed"? It could say "This will add
this file, it is a copy of another file. It will delete this other file,
where this file was copied from", but that doesnt explain any more than
the current "file has local modifications"
My reasoning there is that we'd probably want the --dry-run output to
look the same as the normal output- the normal output doesnt have extra
information such as "and the local modifications are lost" or "and the
local modifications are preserved" or "and the physical file has been
preserved, though it has been removed from version control"- this is all
possible to determine through inspection after-the-fact, and I don't
think normal (non-dry) output should be cluttered with all that extra
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Mar 12 18:31:45 2006