[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:55:02 CEST

actually CVS works very well for this... Basically what I want is to
have the files checked out read only be default and require them to
lock them prior to working on them.

Now I like some of Subversion's features... Especially the browse
feature... And it seems it will work just fine. There is an entire
section in the manual on how to do this.

However is it possible to prevent users that have write access from
changing file properties...? that is where I am confused, because at
first look it appears anyone with write access can change any of the
file properties?

Or am I missing something.

On 7/20/05, Patrick Burleson <pburleson@gmail.com> wrote:
> On 7/20/05, Phil <plabonte@gmail.com> 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?
>
> You know, SVN may not be the right product for you. Sounds like you
> need a central controlled designed system. This is just not how SVN is
> designed to be used. You'll be fighting it all the way.
>
> I don't know of any free systems that do the central server system,
> but you might want to look into Perforce if you need this kind of
> design.
>
> Patrick
>

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

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