Ben Collins-Sussman wrote:
>On 10/16/05, Ingo Adler <dev@synacon.ch> wrote:
>
>
>>(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.
>>
>>
>
>That's because it's none of your business. Some user has created a
>lock in the repository; that user might have 13 different working
>copies, and it's his private business as to which working copy
>actually contains the associated lock-token. Why do you want to know?
> Why does it matter?
>
>You already know which user locked the file, so either call him and
>ask him to release the lock, or forcibly break (or steal) the lock
>yourself.
>
>
OK for me.
>>(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 agree that this is a bug. The full path to the repositorty is a
>minor security bug that we should fix. And I agree that it doesn't
>help the user at all.
>
This was the point. Thank you and good night.
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:53:13 2005