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

Re: Documentation about the 'Lock' feature

From: Phil <plabonte_at_gmail.com>
Date: 2005-07-20 20:58:30 CEST

yes I want to prevent them from breaking and stealing locks yes. There
is a way of doing that?

Email? cool... I have not seen that feature... I can get an email when
a file is changed? or commited?

Yes well I have found if you provide the developpers an inch they will
take a mile and the higher ups are developpers too and they do not
give them any sh#t when they screw up, it is usally blamed on me for
giving them too much access...

On 7/20/05, Ben Collins-Sussman <sussman@collab.net> wrote:
> On Jul 20, 2005, at 1:42 PM, Phil wrote:
> > yes I want to disable all concurrency...
> >
> > And on that note, how can I disable users from changing file
> > properties in subversion... I mean if I give a user write access can
> > they change the files properties?
> >
> >
> Yes, they can, and there's no way to stop them. Either they have
> write access to the file (can commit changes to a file's text and
> properties), or they don't have write access to the file (they cannot
> commit any changes to text or properties.)
> It sounds like you're trying to "control developers with an iron
> fist". If they change a property, wouldn't you see an email saying
> so, and wouldn't you scold the user?
> (Are you also planning to prevent users from breaking and stealing
> locks?)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 20 21:00:24 2005

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

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