most of our documents are binairies so that concurrency does not
matter really...
And merging for binairies is not possible in our case.
Thanks.
On 7/20/05, David Weintraub <qazwart@gmail.com> wrote:
> You sure you want to disable all concurrency? I wouldn't do that
> unless there's a requirement at your company that requires file
> locking. Locking gives you a false sense of security in concurrency
> and is a big administrative headache. (See
> <http://svnbook.red-bean.com/en/1.1/ch02s02.html#svn-ch-2-sect-2.2>).
> Almost all modern version control systems now eliminate the need for
> file locking.
>
> I have a pre-commit Perl script that will verify that properties are
> correctly set (as well as a few other rather useful things). You can
> easily set the hook to make sure that the svn:needs-lock property is
> set on all files, but not on directories. If you're interested, send
> me an email, and I'll send you the script.
>
> 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?)
> > >
> > >
> >
>
>
> --
> --
> David Weintraub
> qazwart@gmail.com
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 20 22:02:25 2005