[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Exclusive Locking

From: <kfogel_at_collab.net>
Date: 2004-08-25 22:32:51 CEST

"Seth de l'Isle" <seth.delisle@ge.com> writes:
> Is there any issue of ownership? I mean would work on this feature by
> someone other than the origal author be ill-received?

Fortunately there's no issue of ownership. No one feels territorial
about the locking design as it stands right now. Many cooks were
involved in that broth :-). It's just a matter of taking the time to
nail down the details and turn it into code. New contributors are
welcome.

See http://svn.collab.net/repos/svn/trunk/notes/locking-design.txt for
the current state of that plan. We intend to get back to it soon
(within a month?).

> Sadly, we're not debating when to roll-out but rather what to roll-out.
> Subversion is still a front-runner because our developers are
> spread accross a few countries. I'd still like to create an
> estimate of the effort involved in adding the feature sooner.
> I'll also be gathering information on workarounds and as Mark
> suggested ways to, um, educate my users.

One thing you might want to do is post to the users@ list describing
your locking needs in detail. A lot of people have come up with
strategies for getting what they need even in the absence of
first-class locking support, and would be happy to share. It may
possibly be that you can accomplish what you need with properties and
hooks, for example (or it may not -- without knowing the exact needs,
it's hard to make general statements).

Good luck,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 26 00:11:22 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.