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 565AD200B21 for ; Fri, 10 Jun 2016 22:42:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 54EB7160A38; Fri, 10 Jun 2016 20:42:35 +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 27D74160A15 for ; Fri, 10 Jun 2016 22:42:34 +0200 (CEST) Received: (qmail 58367 invoked by uid 500); 10 Jun 2016 20:42:28 -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 58356 invoked by uid 99); 10 Jun 2016 20:42:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Jun 2016 20:42:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 90D4CC2D32 for ; Fri, 10 Jun 2016 20:42:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wandisco.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id ZhLQBdyXwFQH for ; Fri, 10 Jun 2016 20:42:25 +0000 (UTC) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 7170C5F46E for ; Fri, 10 Jun 2016 20:42:24 +0000 (UTC) Received: by mail-it0-f43.google.com with SMTP id z189so5216021itg.0 for ; Fri, 10 Jun 2016 13:42:24 -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=axVtTHHnvvno7LxoAjFOq7e4bK0yWX4up5DuW0pvtNE=; b=RUy16nIORLBVYsB9zNV8EDo9Q0R4oTwohUyuRsCcQnqMzRrK9ximtcm8FDAJDpC0i0 nPOTyz5wvOLgaWvoAywQa5p+xpSVh5nxxqETDzyuKxR81l8AlwdFNtiV0ObcAqw8aYZR 4+N9PQ0ix/g83Rbr/693JIxwKXge+ZDjTePdQ= 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=axVtTHHnvvno7LxoAjFOq7e4bK0yWX4up5DuW0pvtNE=; b=EfPj1ExBFbrfzAkL/UCzxdF7jIh+n7z1jUtHexnQN57kE+cJO7LHaYxFTLUwNwL/ks CEA1/qimplslgcnpDvWw+0JC5PQbc5qFAYf4+ZwBo7VedhfhjOAmnX2D99vKtX4GKQZA 5l3ueiwgOa5VybYChvFFck7nAqRaeT5qVho8khJblwalt3vmuXLBM6LsO8RviXdLiIUq lcE9gCJnwVBzIXpZRPbXDnBGHDC5Nw12cIFxO1WcIgLPkw943XqP9wsZObHVyTQXqgNo VzeGsmTpo5+orYcOJEarCC+khxNoPeOgLH2YMH+2INAkVMB8BhBlJuLIhOgYxKy9U8ih yKnA== X-Gm-Message-State: ALyK8tLrtWwG3IM4GXD/jS4Fx9oxpc6SIURRFbXg+ebwoTTEWijzXOfO6Eec0gZTeNxBIBINwZV+DbqsozeWVb9PJePY9pAZLheUq6//+xpfa8Z2HBJ3ikgJq3cpVX5pcAO39x29gWFQp6OuLa7F1aY/yA== X-Received: by 10.36.44.9 with SMTP id i9mr1643145iti.27.1465591343363; Fri, 10 Jun 2016 13:42:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.111.18 with HTTP; Fri, 10 Jun 2016 13:42:22 -0700 (PDT) In-Reply-To: References: <5b401c90-6eb8-494d-b010-2d36e36ad3af@googlegroups.com> From: Doug Robinson Date: Fri, 10 Jun 2016 16:42:22 -0400 Message-ID: Subject: Re: which version control supports file locking and who has it locked To: Mark McKeown Cc: Andreas Stieger , users@subversion.apache.org Content-Type: multipart/alternative; boundary=001a113f64646850a20534f293a8 archived-at: Fri, 10 Jun 2016 20:42:35 -0000 --001a113f64646850a20534f293a8 Content-Type: text/plain; charset=UTF-8 Mark: Nice. And ClearCase with Dynamic Views as Brane reminded me. Doug On Fri, Jun 10, 2016 at 4:36 PM, Mark McKeown wrote: > 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. >> > > -- *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. --001a113f64646850a20534f293a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mark:

Nice.=C2=A0 And ClearCase with Dy= namic Views as Brane reminded me.

Doug
=

On Fri, Jun 10, 2= 016 at 4:36 PM, Mark McKeown <mark.mckeown@wandisco.com> wrote:
Hi Doug,=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0So if I remember co= rrectly p4 supports this, when you "p4 edit" a file it will tell = you if anyone else has already done "p4 edit" on the file.
<= div>
cheers
Mark
On Fri, Jun 10, 2016 at= 8:15 PM, Doug Robinson <doug.robinson@wandisco.com> wrote:
The dichotomy is due to the expression of "knowing who is actually workin= g on a file".

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

<= /div>
However, you really don't know who is working on the file.=C2= =A0 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 work= ing on the file in their sandbox.=C2=A0 None of the discussed SCMs here sup= port those semantics.

<= div class=3D"gmail_quote">On Mon, Jun 6, 2016 at 12:17 PM, Andreas Stieger = <Andreas.Stieger@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=A0SENIOR 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.





--
= DOUGLAS B. ROBINSON=C2=A0SENIOR PRODUCT MANA= GER




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.

--001a113f64646850a20534f293a8--