From users-return-25137-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Fri Sep 2 20:23:04 2016 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5385619661 for ; Fri, 2 Sep 2016 20:23:04 +0000 (UTC) Received: (qmail 26249 invoked by uid 500); 2 Sep 2016 20:22:58 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 26212 invoked by uid 500); 2 Sep 2016 20:22:58 -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 26196 invoked by uid 99); 2 Sep 2016 20:22:58 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2016 20:22:58 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 3288AC031E for ; Fri, 2 Sep 2016 20:22:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id fZJw4qLO7-mA for ; Fri, 2 Sep 2016 20:22:56 +0000 (UTC) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id ABAAC5F36A for ; Fri, 2 Sep 2016 20:22:55 +0000 (UTC) X-Envelope-From: stsp@elego.de Received: from jim.stsp.name (jim.stsp.name [217.197.84.42]) (authenticated bits=0) by einhorn.in-berlin.de (8.14.4/8.14.4/Debian-8) with ESMTP id u82KMev8001621 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 2 Sep 2016 22:22:42 +0200 Received: from localhost (jim.stsp.name [local]) by jim.stsp.name (OpenSMTPD) with ESMTPA id 0d2a160f; Fri, 2 Sep 2016 22:22:40 +0200 (CEST) Date: Fri, 2 Sep 2016 22:22:40 +0200 From: Stefan Sperling To: Alfred von Campe Cc: Bert Huijben , Israel Sadeh , users@subversion.apache.org Subject: Re: SVN Feature Request: Selecting the revision for pinning externals Message-ID: <20160902202239.GM29323@jim.stsp.name> Mail-Followup-To: Alfred von Campe , Bert Huijben , Israel Sadeh , users@subversion.apache.org References: <021601d204f1$11da3bf0$358eb3d0$@qqmail.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.2 (2016-07-01) On Fri, Sep 02, 2016 at 01:48:03PM -0400, Alfred von Campe wrote: > On Sep 2, 2016, at 4:07, Bert Huijben wrote: > > > > A single argument specifying a revision may only work for very specific scenarios. The --pin-externals feature also works when you have dozens of externals, all pointing towards different repositories. > > Right, but could you consider the following scenario? We typically > create tags after a successful release build, and it would be great > that the tag had all the externals pinned to those that were used at > the time of the build. If you need a specific set of property changes in your tag, you can create a working copy which contains the necessary changes and then copy this working copy to a tag. svn co trunk-url working-copy cd working-copy svn propedit/propset svn:externals ... svn cp . ^/tags/1.0.0 We cannot automate details of everybody's build processes in SVN. Sorry.