Karl Fogel <kfogel@newton.ch.collab.net> writes:
> Branko Čibej <brane@xbc.nu> writes:
> > 1. A lock must not create a new revision.
>
> Is this really a requirement? I used to think so, but now I'm not so
> sure.
>
> The two reasons I've heard so far are:
>
> 1. It causes noise in the logs and in the commit emails.
> 2. It "uses up" revision numbers, or makes them less meaningful.
If locks were regular versioned properties, I guess I'd be annoyed at
running 'svn up' and seeing millions of "_U" codes come down every
day. It somehow violates my intuition about locks; I feel like locks
should be a super-lightweight communications system, just an ephermal
layer smoothly floating above the filesystem. 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. Versioning the state of the communication system feels
way too heavy and cumbersome to me.
Just my gut feeling.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 13 19:08:40 2002