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

Re: Locking.. but not commiting.

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 25 Mar 2008 08:29:53 -0400

On Tue, Mar 25, 2008 at 5:43 AM, Jon Hardcastle <jd_hardcastle_at_yahoo.com> 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)?

---------------------------------------------------------------------
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:25 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.