Hi Herman,
please remember to "reply to all" when posting to the list in order for
everyone to be able to follow the discussion.
Indeed there is no restriction on the ability to set or release a lock.
AFAIR there is even some way to "steal" a lock which should of course be
handled with care.
In SVN there is no concept of file or directory ownership; instead you
can set access rights with directory granularity (see the manual for
more details).
Although I can't tell exactly I strongly guess that only those can
set/release locks on a file who actually have commit permission to the
containing directory (everything else would IMHO not make too much
sense).
Best regards,
Thomas
_____
From: Herman - Temp [mailto:Herman_at_synergixtech.com]
Sent: Wednesday, January 16, 2008 11:34 AM
To: 'Thomas Hemmer'
Subject: RE: Question about Subversion features
Hi Thomas,
Does anybody in the team can do the lock file? Or only the owner of the
file (person who create that particular file) ? Or maybe any permission
need to be given to do the lock for the project team member?
Thanks,
Herman
-----Original Message-----
From: Thomas Hemmer [mailto:themmer_at_go-engineering.de]
Sent: Wednesday, 16 January, 2008 5:54 PM
To: 'Peter Connolly'; 'Herman - Temp'
Cc: users_at_subversion.tigris.org
Subject: RE: Question about Subversion features
Peter, Herman,
there is no reason at all to avoid subversion ;-)
Although SVN does not provide any means to *automagically* lock a file
on check out it still supports a locking mechanism. In fact this does
not impose any restriction: after having checked out some file, anyone
is free to make their changes to it without doing any harm to you. The
only rule to be obeyed is that whoever is going to edit the file
*must* set a lock before (For safety, you might perform an "svn update"
prior to locking). The one who "wins the race" does his/her changes and
commits them when done.
As soon as the lock owner has released it it's your turn.
Happy versioning,
Thomas
> -----Original Message-----
> From: Peter Connolly [mailto:psconnolly_at_gmail.com]
> Sent: Wednesday, January 16, 2008 5:37 AM
> To: Herman - Temp
> Cc: users_at_subversion.tigris.org
> Subject: Re: Question about Subversion features
>
> If you want each developer to have exclusive use of a file that they
> are changing and you want to avoid merging, then you should probably
> be looking at RCS and avoiding Subversion and CVS.
>
> On Jan 15, 2008 6:54 PM, Herman - Temp <Herman_at_synergixtech.com>
> wrote:
> >
> >
> > Hi,
> >
> > I'm currently doing evaluation on versioning control system.
> > Subversion is one of my consideration to be used in the
> company where
> > i'm employed. There are around 10 developers in this company.
> > Occasionally, when a file need to be merged, the old code is
> > overwritten by the new code. So, I want to know whether
> Subversion has
> > the feature to automatic lock a files that is already
> checkout-ed for
> > editting? Or Is there any suggestion to reduce the code merging to
> > happen? How does Subversion handle binary file? (Note:
> Binary file cannot be merge normally, right?).
> >
> >
> > Regards,
> >
> >
> > Herman.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
GO Engineering GmbH - Stolzenbergstr. 13/IV - 76532 Baden-Baden
Geschäftsführer:
Helmut Gerstner, Dipl.-Ing. (FH)
Ralf Wörner, Dipl.-Ing. (FH)
Registergericht: Mannheim HRB 201811
Received on 2008-01-16 11:49:04 CET