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

Re: Locking: RFC: svn:needs-lock behaviors (Updated)

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-02-02 23:09:50 CET

"Brian W. Fitzpatrick" <fitz@collab.net> wrote on 02/02/2005 05:05:53 PM:

> On Wed, 2005-02-02 at 16:00, Mark Phippard wrote:
> > "Brian W. Fitzpatrick" <fitz@collab.net> wrote on 02/02/2005 04:53:37
> >
> > [snip]
> >
> > > Propset:
> > > - Setting the svn:needs-lock property sets the file to read-only
> > > (It also canonicalizes the value to '*')
> >
> > Before setting the file to read-only, shouldn't it check to see if it
> > locally modified?
> Hmm. I'm not sure about that--if the prop is set, and the user has
> local mods, isn't it safe to assume that the user is doing it
> intentionally?

Sure, but if I am editing the file, as indicated by the local mods,
doesn't it stand to reason that I would not want the file to be made
read-only until I commit? In your scenario, are you assuming that after
running svn propset, I would have to run svn lock to make the file
read-write before I commit?



Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 2 23:11:03 2005

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.