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 B5EA0200AE1 for ; Mon, 6 Jun 2016 15:47:16 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B44F2160A24; Mon, 6 Jun 2016 13:47: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 D62A9160A1E for ; Mon, 6 Jun 2016 15:47:15 +0200 (CEST) Received: (qmail 91968 invoked by uid 500); 6 Jun 2016 13:47:15 -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 91958 invoked by uid 99); 6 Jun 2016 13:47:14 -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; Mon, 06 Jun 2016 13:47:14 +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 4B2A2C20C4 for ; Mon, 6 Jun 2016 13:47:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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: spamd1-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=wandisco.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id R3dpSgzVnViR for ; Mon, 6 Jun 2016 13:47:09 +0000 (UTC) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 6C4395F246 for ; Mon, 6 Jun 2016 13:47:09 +0000 (UTC) Received: by mail-io0-f181.google.com with SMTP id 5so17152899ioy.1 for ; Mon, 06 Jun 2016 06:47:09 -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=rdceQnsW4v3ILh8zS737CP6Rd8W4AoQTGoZpftN9Ft4=; b=LcFvuMwtmYtKBftpASxxv21RPXUfNVnqBOi8xloeGQZP6QVglxgF3HEoq5H9dnnF2h ae/Ny8i2rQ8LB9Llujk4XOurZKhM5Y5YDsd7atxDm6SGmSXSy+DYMt/5Y3roWlEU2Ftt jIQuCU9Vb7xgyqQUV44M6I6Yk64H5Uc13yHuQ= 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=rdceQnsW4v3ILh8zS737CP6Rd8W4AoQTGoZpftN9Ft4=; b=QJsbS/3QMHnv1LYjcG+JwFrrDU6+I3mFajQBZeHLsT2OyYCRDwUw4CzHqYXfd/EtpO w3ftlmlGvBWJOP4Ql1zhd+WPEIerS8q0UugmQ/fJKgni6WbFsUv0E7AGU1BzM2yiiFXe Yc518zB2TN82DDYVE8iGXiP/olUreaeCOoAluuLcUS2jCyrmBXU4Mhfq7RIMETFhOzzt aslDhbDyMI3AixQI2c/bV0VtrJ4u1gdZtOTob3AXz92TfLf5ZtAswMZCo/yCOrpt3Asc m3e6mIuGIUHVamBIlMCls3T/UqNvJaLXrCEsAvpPmEDMH/cy4HyrJbyt1XhXtqV/zmd4 Bgzg== X-Gm-Message-State: ALyK8tK1aKxOQg7iAH3rgHFFQ2S68PWWa/9lw/6BeLFGsqiAHGtrrZxYR5wMKV0WFCw8+Sz4yQtT33gwrthvqBhq1KsdGuVCX7klOqTOsxDzpPwKcUnG9DEfNq3nW+pbSrWIOigz3bhEmT9pmgqQmktY0A== X-Received: by 10.107.16.99 with SMTP id y96mr4386880ioi.36.1465220828549; Mon, 06 Jun 2016 06:47:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.197.7 with HTTP; Mon, 6 Jun 2016 06:47:07 -0700 (PDT) In-Reply-To: References: <5b401c90-6eb8-494d-b010-2d36e36ad3af@googlegroups.com> From: Doug Robinson Date: Mon, 6 Jun 2016 09:47:07 -0400 Message-ID: Subject: Re: which version control supports file locking and who has it locked To: Andreas Stieger Cc: users@subversion.apache.org Content-Type: multipart/alternative; boundary=001a113e782e00eeff05349c4fd4 archived-at: Mon, 06 Jun 2016 13:47:16 -0000 --001a113e782e00eeff05349c4fd4 Content-Type: text/plain; charset=UTF-8 Andreas: On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger wrote: > > or knowing who is actually working on a file. > > Incorrect, this is shown in both TortoiseSVN and svn cli. > 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). 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. Doug -- *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. --001a113e782e00eeff05349c4fd4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Andreas:

On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger <A= ndreas.Stieger@gmx.de> wrote:
> or knowing who is actually working on a file.

Incorrect, this is shown in both TortoiseSVN and svn cli.

To be more precise, you can know who, in the past= , has made changes to files and
checked those change into the rep= ository.=C2=A0 You cannot know who has made changes
in their working cop= y and has not yet checked them back into the repository (they
may never = do so).

To know who is actually working o= n a file requires a level of integration 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 th= e moment.

Doug
--
DOUGLAS B.= ROBINSON=C2=A0SENIOR PRODUCT MANAGER

<= div>


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.

--001a113e782e00eeff05349c4fd4--