[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:43:22 CEST

And by that I mean changing svn:needs-lock and other properties...

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?
>
>
>
>
> On 7/20/05, Ben Collins-Sussman <sussman@collab.net> wrote:
> >
> > On Jul 20, 2005, at 1:29 PM, Phil wrote:
> >
> > > I did and this is what I am try to issue:
> > >
> > > svn propset svn:needs-lock * reponame
> > >
> > > does nto work...?
> > >
> > > I need specific help... what specifically do I need to issue as a
> > > command to set the property to all the subdirectories below my
> > > repository that I have called 'reponame'?
> > >
> > > everything I tried gives me the error:
> > > '.' is not a working copy
> > >
> >
> > You can only lock files, not directories. Therefore, it only makes
> > sense to set 'svn:lock' property on files.
> >
> > It sounds, then, like you want to run 'svn propset' on every file in
> > your working copy. To do this, use your shell, or write a simple
> > script of some sort.
> >
> > (Are you really certain that you want to completely disable
> > concurrency on the whole project? You want to force people to lock
> > *every* file before they begin editing?)
> >
> >
>

---------------------------------------------------------------------
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:46:26 2005

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