--- Andy Levy <andy.levy_at_gmail.com> wrote:
> On Tue, Mar 25, 2008 at 5:43 AM, Jon Hardcastle
> <jd_hardcastle_at_yahoo.cm> wrote:
> > > Hello Chaps!
> > >
> > >
> > > I hope I am in the right place!
> > >
> > > I'd like to engineer it so that i can have
> READONLY
> > > access to an area, and yet. Still be able to
> lock
> > > files in it?
> > >
> > > I have tried this..
> > >
> > > <LimitExcept GET PROPFIND OPTIONS
> REPORT
> > > LOCK>
> > > Require valid-user
> > > </LimitExcept>
> > >
> > >
> > > but it doesn't seem to work. Any help or clues?
>
> A) This is a Subversion server question, not TSVN.
> B) What's your use case? Locking is only required if
> a user is going
> to modify and commit changes. If they're locking a
> file, but not
> allowed to make any changes, what's the point of
> locking (beyond
> annoying those who *can* make changes)?
>
a) Sorry :-/
b) The use case is if our branches contain mergeable
and non-mergeable files. All users must work on
branches, only sysadmin can commit to trunk - to keep
it at a minimum level of 'excellence'. So because of
this, if a user wants to 'work' on a binary file in
their branch. It would be great if they could lock it
in the main - as a signal to others and then work on
it in their branch..
hope that makes sense?
-----------------------
N: Jon Hardcastle
E: Jon_at_eHardcastle.com
'The writing is on the wall...'
-----------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-25 13:50:07 CET