subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Robinson <doug.robin...@wandisco.com>
Subject Re: which version control supports file locking and who has it locked
Date Fri, 10 Jun 2016 19:15:48 GMT
The dichotomy is due to the expression of "knowing who is actually working
on a file".

I agree that if locking is used then (assuming nobody breaks the lock) you
know who will checkin next.  And, yes, agreed, when they check in is a
social issue.

However, you really don't know who is working on the file.  This may all
seem meta-physical but I've seen requirements for SCM systems where it
really was necessary to know exactly who was actually working on the file
in their sandbox.  None of the discussed SCMs here support those semantics.

On Mon, Jun 6, 2016 at 12:17 PM, Andreas Stieger <Andreas.Stieger@gmx.de>
wrote:

> Doug,
>
> Doug Robinson wrote:
> > To be more precise, you can know who, in the past, has made changes to
> files and
> > checked those change into the repository.  You cannot know who has made
> changes
> > in their working copy and has not yet checked them back into the
> repository (they
> > may never do so).
>
> I am not sure why you would introduce this dichotomy here, it is
> irrelevant. OP asked for locking support. Subversion supports locking, lock
> hinting (svn:needs-lock), lock communication/discovery (display of who,
> when and why). In the cli, hooks and GUI clients. Whether or not actual
> changes were done in any working copy is irrelevant, and a delay in
> submission a mere social/project problem.
>
> > To know who is actually working on a file requires a level of
> integration that is not
> > found in SVN, Git or CVS.  I have a vague recollection of an SCM that
> did enable
> > such information but I'm not remembering which one it is at the moment.
>
> Rather, if the project policy is such that locking is required, it should
> be implemented accordingly. lock-modify-unlock for the whole project is a
> supported option, albeit not a commonly used one.
>
> Andreas
>



-- 
*DOUGLAS B. ROBINSON* SENIOR PRODUCT MANAGER

*T *925-396-1125
*E* doug.robinson@wandisco.com

*www.wandisco.com <http://www.wandisco.com/>*

-- 


Learn how WANdisco Fusion solves Hadoop data protection and scalability 
challenges <http://www.wandisco.com/hadoop/wd-fusion>

Listed on the London Stock Exchange: WAND 
<http://www.bloomberg.com/quote/WAND:LN>

THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE 
PRIVILEGED.  If this message was misdirected, WANdisco, Inc. and its 
subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. 
 If you are not the intended recipient, please notify us immediately and 
destroy the message without disclosing its contents to anyone.  Any 
distribution, use or copying of this e-mail or the information it contains 
by other than an intended recipient is unauthorized.  The views and 
opinions expressed in this e-mail message are the author's own and may not 
reflect the views and opinions of WANdisco, unless the author is authorized 
by WANdisco to express such views or opinions on its behalf.  All email 
sent to or from this address is subject to electronic storage and review by 
WANdisco.  Although WANdisco operates anti-virus programs, it does not 
accept responsibility for any damage whatsoever caused by viruses being 
passed.

Mime
View raw message