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 DF56B200B11 for ; Mon, 13 Jun 2016 22:49:16 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DDD7B160A3C; Mon, 13 Jun 2016 20:49:16 +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 D5687160A1A for ; Mon, 13 Jun 2016 22:49:15 +0200 (CEST) Received: (qmail 8762 invoked by uid 500); 13 Jun 2016 20:49:10 -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 8752 invoked by uid 99); 13 Jun 2016 20:49:09 -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; Mon, 13 Jun 2016 20:49:09 +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 4E57A1800B5 for ; Mon, 13 Jun 2016 20:49:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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: 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 lAuiH_HsV0Q4 for ; Mon, 13 Jun 2016 20:49:06 +0000 (UTC) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 90D835F3F1 for ; Mon, 13 Jun 2016 20:49:05 +0000 (UTC) Received: by mail-it0-f50.google.com with SMTP id z189so60184952itg.0 for ; Mon, 13 Jun 2016 13:49:05 -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=bVYd0JCz4A1hp67u7gcrwJ9d4bvGWu6ELO4b8BjzcPE=; b=St+O0zvpZ6qqGJB0YBa/QrqgK+nKfBisPPyebBKViT71GdpV5arBzuBzoU8ghXtA5G vmbw87UWFQVUbdL9Rkvo7e2uTY3YXGiLtIP/gK8sPjS/udLHKyGd+HiB75Xrd/v/B8LL wHHNaC2WPNAIi9nIEqAS8v71f87NRS5JH9FlQ= 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=bVYd0JCz4A1hp67u7gcrwJ9d4bvGWu6ELO4b8BjzcPE=; b=h8bekvf3JpDe7TD+oEyDNkF+n++/rpnLCniMtVRGkdOiMAHhnuOZOrSge7wmNnM68w 5NG+BUc2/5dffajuKwzxJ3DbhXrIZrROoqVgS5p4ItvfE33Hn1dhCThnA6gklFynd58Q XkjvAsaKUeOfOLVO3YfCDXmHbWSQRWDWKWBEp7l8IAcZ22HCAQOHIZrvzW3KBuVoD+PR r2hEzBMQTmha1sZaHJcIWGRoNi9ndg8NAeF7aApwm+zpHXvtgmTxMcSAJ9bpsuZmaifQ 5UPWK7A1NGW0SexDXiZNJ2OkOszAP9KEAGG4tuCsaVgUsCaIiQNBL8dXWWF2tWTYkssv LhkQ== X-Gm-Message-State: ALyK8tLWTREYJk1L9QaA0CGfhXpRod7Yr0P7f/Z6gMpwjGly5QU9Zd8SLLtaLa1/ZBX/8pdPZLkXf6FGv6rUNQbtKHbN5LukQ1ypecHcHlOtaH7C16hwxrsHhvlSHGUA+f8HNISVW00HJjvaFYgApjv+kw== X-Received: by 10.36.227.12 with SMTP id d12mr2526011ith.49.1465850944146; Mon, 13 Jun 2016 13:49:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.111.18 with HTTP; Mon, 13 Jun 2016 13:49:03 -0700 (PDT) In-Reply-To: References: <5b401c90-6eb8-494d-b010-2d36e36ad3af@googlegroups.com> From: Doug Robinson Date: Mon, 13 Jun 2016 16:49:03 -0400 Message-ID: Subject: Re: which version control supports file locking and who has it locked To: Johan Corveleyn Cc: Mark McKeown , Andreas Stieger , "users@subversion.apache.org" Content-Type: multipart/alternative; boundary=94eb2c111716d1efcb05352f04a2 archived-at: Mon, 13 Jun 2016 20:49:17 -0000 --94eb2c111716d1efcb05352f04a2 Content-Type: text/plain; charset=UTF-8 Johan: On Mon, Jun 13, 2016 at 2:30 PM, Johan Corveleyn wrote: > On Mon, Jun 13, 2016 at 5:29 PM, Doug Robinson > wrote: > > > > Johan: > > > > The "svn lock" enables all people considering working with a file to > > be able to see who currently has the file locked. But they cannot see > > anyone who is working on the file but does not own the lock. > > > > Reading the "p4 edit" man page: > > > > https://www.perforce.com/perforce/r16.1/manuals/cmdref/p4_edit.html > > > > we see that the expected use is "p4 edit; ; p4 submit" and > that > > "p4 edit" updates the Perforce database to mark the file as being edited > > by that account in that workspace. That means that any other Perforce > > user can see *all* of the other accounts working on that file (this is > *not* > > the same as a lock) by issuing the "p4 opened -a file" command. > > > > The ClearCase Dynamic View situation is pretty much the same as what > > I have described above for Perforce. > > Okay, so IIUC with "p4 edit" multiple users can start editing the file > (Alice, John and Jim), and they can all indicate concurrently that > they're editing the file, and other users can see that Alice, John and > Jim all have the file opened for editing. Interesting, but I fail to > see how that helps with non-mergeable files, where you want to lock it > out for one person to work on it at the same time. > Or they can check to see who's editing it before checking it out. > Remember the question from the OP: "in Tortoise SVN, there is no > method of locking a file until it has been changed . > or knowing who is actually working on a file. is this feature > available on any other version control , GIT , CVS ?" > There are 2 parts to that question: 1. no method of locking 2. no way to see who's actually working on the file The former is just wrong: SVN has locking and TortoiseSVN definitely has that implemented. > He seems to be asking for locks, i.e. one developer locks it until he > has completed his change. > I just didn't assume that the OP only was talking about locking. If they were then the 2nd comment is strange, but, well, ok. Done. Apart from that: AFAICS the remark "But they cannot see anyone who is > working on the file but does not own the lock" applies to all systems > under discussion. With Perforce, I'm guessing that I can just as well > start editing the file with some text editor, outside of p4's > knowledge, right? That's just the same as starting to edit an > svn:needs-lock file without taking the svn lock (note that an > "svn:needs-lock file" is by default read-only on the filesystem in an > svn working copy, so you have to explicitly make it writeable). > I'm not sure about Perforce's implementation. However, just for comparison: with ClearCase Dynamic Views you can *not* edit the file without a checkout. The Dynamic View implementation is via an actual OS file system so you can't beat it. And everyone can see that checkout. Doug > > -- > Johan > -- *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. --94eb2c111716d1efcb05352f04a2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Johan:

On Mon, Jun 13, 2016 at 2:30 PM,= Johan Corveleyn <jcorvel@gmail.com> wrote:
On Mon, Jun 13, 2016 at 5:29 PM, Doug Robinson
<doug.robinson@wandisco.co= m> wrote:
>
> Johan:
>
> The "svn lock" enables all people considering working with a= file to
> be able to see who currently has the file locked.=C2=A0 But they canno= t see
> anyone who is working on the file but does not own the lock.
>
> Reading the "p4 edit" man page:
>
> https://www.perforce.com/per= force/r16.1/manuals/cmdref/p4_edit.html
>
> we see that the expected use is "p4 edit; <edit file>; p4 s= ubmit" and that
> "p4 edit" updates the Perforce database to mark the file as = being edited
> by that account in that workspace.=C2=A0 That means that any other Per= force
> user can see *all* of the other accounts working on that file (this is= *not*
> the same as a lock) by issuing the "p4 opened -a file" comma= nd.
>
> The ClearCase Dynamic View situation is pretty much the same as what > I have described above for Perforce.

Okay, so IIUC with "p4 edit" multiple users can start edit= ing the file
(Alice, John and Jim), and they can all indicate concurrently that
they're editing the file, and other users can see that Alice, John and<= br> Jim all have the file opened for editing. Interesting, but I fail to
see how that helps with non-mergeable files, where you want to lock it
out for one person to work on it at the same time.
Or they can check to see who's editing it before checking i= t out.
=C2=A0
Remember the question from th= e OP: "in Tortoise SVN, there is no
method of locking a file until it has been changed .
or knowing who is actually working on a file. is th= is feature
available on any other version control , GIT , CVS ?"

There are 2 parts to that question:
1.= no method of locking
2. no way to see who's actually working= on the file

The former is just wrong: SVN has loc= king and TortoiseSVN definitely
has that implemented.
= =C2=A0
He seems to be asking for locks, i.e. one deve= loper locks it until he
has completed his change.

I just didn&#= 39;t assume that the OP only was talking about locking.
If they w= ere then the 2nd comment is strange, but, well, ok.=C2=A0 Done.=C2=A0
=

Apart from that: AFAICS the remark "Bu= t they cannot see anyone who is
working on the file but does not own the lock" applies to all systems<= br> under discussion. With Perforce, I'm guessing that I can just as well start editing the file with some text editor, outside of p4's
knowledge, right? That's just the same as starting to edit an
svn:needs-lock file without taking the svn lock (note that an
"svn:needs-lock file" is by default read-only on the filesystem i= n an
svn working copy, so you have to explicitly make it writeable).

I'm not sure about Perforce's implementati= on.=C2=A0 However, just for
comparison: with ClearCase Dynamic Vi= ews you can *not* edit the file
without a checkout.=C2=A0 The Dyn= amic View implementation is via an actual
OS file system so you c= an't beat it.=C2=A0 And everyone can see that checkout.

<= /div>
Doug
=C2=A0

--
Johan



--
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=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.

--94eb2c111716d1efcb05352f04a2--