Michael Wood wrote:
>>Yes, definitely. You could even be more explicit:
>>
>> "Someone else has updated this file. Please run 'svn update'" (or
>>something similar)
>>
>>
>But in this case this error does NOT mean that someone else updated
>anything. It was about a directory, not a file. The directory was not
>up to date because some stuff had been committed inside of it (instead
>of the directory being committed). The files in the directory that were
>committed, were therefore at revision X+n, but the directory was still
>at revision X.
>
That means svn should give different messages for files and directories.
I think, this shouldn't be too difficult to implement. BTW: Your
explanation above would be a good starting point for an improved svn
error reporting.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 6 18:20:09 2003