Re: [Issue 533] New - implement reserved checkouts

Peter Davis wrote:

>On Tuesday 13 August 2002 10:07, Ben Collins-Sussman wrote:
>
>
>>They're not important
>>enough to record and remember over time. Do I *really* care that on a
>>certain date, certain people were communicating in a certain way? Not
>>me, at least.
>>
>>
>
>The reason I use Subversion and similar systems is to keep track of the entire
>history of a project. That's why I'm developing an issue tracker based on
>Subversion, because I want /everything/ to be versioned. So maybe I'm a
>little obsessive/compulsive... :) But yes, personally I would like to be
>able to see lock history.
>

You already see the history of how files were changed. If you enforce
strict locking, that's lock history, too.

>If locks end up not using normal revisions/properties, then maybe they could
>have a separate system that stores all the locks made for each revision, and
>doesn't "forget" them.
>

Write a "lock-sentinel" hook script and have it log lock activity, if
you want it. There's no need to make this part of the repository. We do
something similar with the tweak-log.cgi script.

>>Versioning the state of the communication system feels
>>way too heavy and cumbersome to me.
>>
>>
>
>I see locks as more than a communication system. For normal communication,
>which even I agree does not need to be versioned (although I do save all of
>my email), email and IM work fine. But locks also tell me when and why a
>person has locked something, and can generally be used to see what a person
>is working on.
>

How is this different from a communications system?

> If someone locks something and doesn't work on it, then
>history could be used to prove that that person is abusing the system.
>

Oh, so you'd overload locks to be a performance evaluation tool, too.
But we have those already, they're called 'svn diff' and 'svn log' (and
someday 'svn blame').

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org