Ben Collins-Sussman wrote:
>On 10/16/05, Ingo Adler <dev@synacon.ch> wrote:
>
>
>>Then I could start to look for it. For instance I could ask 'iar' and
>>point him to the locked file.
>>
>>
>
>What information do you need? The error message has already told you
>(1) the locked path, (2) which repository it's in, and (3) the user
>who locked it. If you need more still more information about the
>lock, you could run 'svn info URL-of-file', and you then know (4) the
>date the lock was created and (5) the lock-comment written by 'iar',
>if he wrote one.
>
>That's 3 pieces of lock information for free, and 2 more if you run
>'svn info URL'. None of these things are useless 'server internal'
>information. All of them are designed to let you know about the
>repository lock that iar made, so you can chat with him if need be.
>
>
(1) It tells the path in the repository. But there is one instance of a
locked file in one working copy somewhere. I don't know where it is.
(2) No, it doesn't tell me which repository it's in. It tells me, where
the repository files are placed on the server. But which server?
I don't really need much more information. It would be nice to have
more, for instance which working copy on which computer. But I really
don't need useless information - the directory where the repository is
placed on the server ('C:/Daten/svnroot/myrepo/db'). That's really some
internal stuff. You could add much of this "free" information to every
subversion message. But you shouldn't. Just tell the user what he needs
to solve his problem. The user's name is good. The path of the file is
OK. The repository path on the server (local to the server) is not OK.
There could be security reasons too to omit this information. I just
took the end-user's perspective.
Ingo.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 16 23:38:30 2005