You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Alex Holst <a...@mongers.org> on 2004/08/27 23:40:41 UTC
RFC: locking-design.txt, On non-locking policies
Someone on IRC, don't recall whom, recently asked me to voice this
request on dev, and I thought this addition to locking-design.txt
describe my wishes best.
Index: locking-design.txt
===================================================================
--- locking-design.txt (revision 10680)
+++ locking-design.txt (working copy)
@@ -111,6 +111,12 @@
be modified by the client. This is a repository policy,
not a user decision. -- brane]
+ Mark certain files/paths with a special svn: property which
+ means "this file cannot be locked." Files with this property
+ cannot be locked and any attemps to 'svn lock' fails with:
+ "Repository policy prevents locking this file." Suggest this
+ be a read-only liveprop whose value is implied by server-side
+ configuration, and can't be modified by the client.
Weird scenarios with lock-tokens/working-copies:
--
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow. http://a.mongers.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: RFC: locking-design.txt, On non-locking policies
Posted by Alex Holst <a...@mongers.org>.
Quoting Greg Hudson (ghudson@MIT.EDU):
> What you really want is a way to prevent people from locking
> files--ideally specific files, but perhaps a blanket protection on the
> whole repository might be enough--and you don't care how it's
> implemented.
Correct. Personally I would just enforce a no-locking policy on the
entire repository, but I can imagine cases where someone might want
locking used for some of the data in their repository.
--
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow. http://a.mongers.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: RFC: locking-design.txt, On non-locking policies
Posted by Greg Hudson <gh...@MIT.EDU>.
On Fri, 2004-08-27 at 19:40, Alex Holst wrote:
> Someone on IRC, don't recall whom, recently asked me to voice this
> request on dev, and I thought this addition to locking-design.txt
> describe my wishes best.
Unfortunately, you copied text by brane which didn't really make sense.
Nobody's done anything about it because it's never clear how to respond
to brane's weird "comments inside design documents" habit.
* "Liveprop" is a DAV-specific term, as best I understand it, and
doesn't belong in the locking design.
* The idea that the unmergeability of a file is "a repository policy,
not a user decision" is bizarre. All file properties are "repository
policies," but the repository belongs to a set of users (some perhaps
more privileged than others).
What you really want is a way to prevent people from locking
files--ideally specific files, but perhaps a blanket protection on the
whole repository might be enough--and you don't care how it's
implemented. I assume we'll have at least the blanket protection
ability in the initial locking implementation.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org