Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EBF6F200B21 for ; Fri, 10 Jun 2016 22:36:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EA81B160A38; Fri, 10 Jun 2016 20:36:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E435A160A15 for ; Fri, 10 Jun 2016 22:36:51 +0200 (CEST) Received: (qmail 45674 invoked by uid 500); 10 Jun 2016 20:36:51 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 45664 invoked by uid 99); 10 Jun 2016 20:36:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jun 2016 20:36:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 50EC6180541 for ; Fri, 10 Jun 2016 20:36:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wandisco.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id JY7bfHWbC_FW for ; Fri, 10 Jun 2016 20:36:47 +0000 (UTC) Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 771355FACD for ; Fri, 10 Jun 2016 20:36:46 +0000 (UTC) Received: by mail-qg0-f47.google.com with SMTP id p34so42458177qgp.1 for ; Fri, 10 Jun 2016 13:36:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wandisco.com; s=gapps; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Z//4LI6KxT4TDLXp0Q5n8+Pdp6W9AXMwz+HvX7F06Us=; b=LnIRaCOpQcYvIjcqKDWgYYaKNhUtAK6w61jMzkzUeNiNz9QqqDBOtgC779YaawbI9r fGF5Vh0ksmv9Rgk461P005yU+OVfF5tv8Pe3oSuJ/FbClKoNIEHl4wfmDkxPttplfk9N Rmyum+ac5V2dZR2tOwKaqsWgoIhfO6vK3zdhM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Z//4LI6KxT4TDLXp0Q5n8+Pdp6W9AXMwz+HvX7F06Us=; b=hb2rBtiUaBqSJk1R8Gt2Hgcvp1jQGqVnfJYDyU1j5A43U6JFkvn9vI+x2+O0DQVou1 Gxk8QiGYszSJmMvb4Pa9W2TGO47IPtRoNi09+2e11itCIH8voSbtQJ6l3QfDpKJZFJWB MPlxQF7xR3G6Ggb4byR4HOZQsOsSHipfWpriTc0x8i0KjYdSmCNmecsz2OYx31iA74Ri mSoFriiel72MMTRZ+X4w2Ebn8ZKEMzaYsNEDDalWyd0eKxUIl6JsYtQJQfF1YHG+2p3H N3DXFU/OYkYYoMFLVHZFaMk55ji6x6Pwg7bGcbLzv64qbghjrIIdisiqnvQ1m9rgUjtH 4eaw== X-Gm-Message-State: ALyK8tJOVps3uacsKPB7rUDBXKEZS8IIrhGgWXAiHCE6GeJTl1AbBpXmFWEIFxVA+NBW89hDkAnDp+SMZ7n8OXOSfLbp2kvwlHdSKVWdZSj4x7AipO1ruF2r9zfEBCEHJpRn0K4IkM/uvdiLPYeZH32PUQ== X-Received: by 10.140.18.244 with SMTP id 107mr3619971qgf.95.1465590999555; Fri, 10 Jun 2016 13:36:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.40.234 with HTTP; Fri, 10 Jun 2016 13:36:38 -0700 (PDT) In-Reply-To: References: <5b401c90-6eb8-494d-b010-2d36e36ad3af@googlegroups.com> From: Mark McKeown Date: Fri, 10 Jun 2016 21:36:38 +0100 Message-ID: Subject: Re: which version control supports file locking and who has it locked To: Doug Robinson Cc: Andreas Stieger , users@subversion.apache.org Content-Type: multipart/alternative; boundary=001a11355d9eea48260534f27e14 archived-at: Fri, 10 Jun 2016 20:36:53 -0000 --001a11355d9eea48260534f27e14 Content-Type: text/plain; charset=UTF-8 Hi Doug, So if I remember correctly p4 supports this, when you "p4 edit" a file it will tell you if anyone else has already done "p4 edit" on the file. cheers Mark On Fri, Jun 10, 2016 at 8:15 PM, Doug Robinson wrote: > 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 > 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 * > > > Learn how WANdisco Fusion solves Hadoop data protection and scalability > challenges > > Listed on the London Stock Exchange: WAND > > > 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. > -- Learn how WANdisco Fusion solves Hadoop data protection and scalability challenges Listed on the London Stock Exchange: WAND 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. --001a11355d9eea48260534f27e14 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Doug,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0So if I remember correctly p4 supports this, when you "p4 ed= it" a file it will tell you if anyone else has already done "p4 e= dit" on the file.

cheers
Mark
=

On Fri, Jun 10, 2= 016 at 8:15 PM, Doug Robinson <doug.robinson@wandisco.com>= wrote:
The dicho= tomy is due to the expression of "knowing who is actually working on a file".
I agree that if locking is used then (assuming nobody break= s the lock) you know who will checkin next.=C2=A0 And, yes, agreed, when th= ey check in is a social issue.

However, you really= don't know who is working on the file.=C2=A0 This may all seem meta-ph= ysical but I've seen requirements for SCM systems where it really was n= ecessary to know exactly who was actually working on the file in their sand= box.=C2=A0 None of the discussed SCMs here support those semantics.

On Mon, Jun 6, 2016 at 12:17 PM, Andreas Stieger <Andreas.S= tieger@gmx.de> wrote:
Doug,=
=C2=A0
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.=C2=A0 You cannot know who ha= s made changes
> in their working copy and has not yet checked them back into the repos= itory (they
> may never do so).=C2=A0

I am not sure why you would introduce this dichotomy here, it is irr= elevant. OP asked for locking support. Subversion supports locking, lock hi= nting (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 me= re social/project problem.

> To know who is actually working on a file requires a level of integrat= ion that is not
> found in SVN, Git or CVS.=C2=A0 I have a vague recollection of an SCM = that did enable
> such information but I'm not remembering which one it is at the mo= ment.

Rather, if the project policy is such that locking is required, it s= hould be implemented accordingly. lock-modify-unlock for the whole project = is a supported option, albeit not a commonly used one.

Andreas



--
DOUGLAS B. ROBINSON=C2=A0SENI= OR PRODUCT MANAGER




Learn how WANdisco Fusion solves Hadoop data protection an= d scalability challenges

L= isted on the London Stock Exchange:=C2=A0WAND<= /p>

THIS MESSAGE AND ANY= ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED.=C2=A0 If= this message was misdirected, WANdisco, Inc. and its subsidiaries, ("= WANdisco") does not waive any confidentiality or privilege.=C2=A0 If y= ou are not the intended recipient, please notify us immediately and destroy= the message without disclosing its contents to anyone.=C2=A0 Any distribut= ion, use or copying of this e-mail or the information it contains by other = than an intended recipient is unauthorized.=C2=A0 The views and opinions ex= pressed 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 WAN= disco to express such views or opinions on its behalf.=C2=A0 All email sent= to or from this address is subject to electronic storage and review by WAN= disco.=C2=A0 Although WANdisco operates anti-virus programs, it does not ac= cept responsibility for any damage whatsoever caused by viruses being passe= d.



Learn how WANdisco Fusion solves Hadoop data protection an= d scalability challenges

L= isted on the London Stock Exchange:=C2=A0WAND<= /p>

THIS MESSAGE AND ANY= ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE PRIVILEGED. =C2=A0If= this message was misdirected, WANdisco, Inc. and its subsidiaries, ("= WANdisco") does not waive any confidentiality or privilege. =C2=A0If y= ou are not the intended recipient, please notify us immediately and destroy= the message without disclosing its contents to anyone. =C2=A0Any distribut= ion, use or copying of this e-mail or the information it contains by other = than an intended recipient is unauthorized. =C2=A0The views and opinions ex= pressed 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 WAN= disco to express such views or opinions on its behalf. =C2=A0All email sent= to or from this address is subject to electronic storage and review by WAN= disco. =C2=A0Although WANdisco operates anti-virus programs, it does not ac= cept responsibility for any damage whatsoever caused by viruses being passe= d.

--001a11355d9eea48260534f27e14--