[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Questions about --pin-externals option

From: Grant Edwards <grant.b.edwards_at_gmail.com>
Date: Tue, 26 Apr 2016 18:32:49 +0000 (UTC)

On 2016-04-26, Branko Čibej <brane_at_apache.org> wrote:
> On 26.04.2016 02:09, Grant Edwards wrote:
>> Thanks again! Now I just have to decided whether to use
>> intra-repository externals or nested working copies to share
>> directories of source code among a group of projects. It may depend on
>> how smartsvn handles tagging/branching that involves externals. I see
>> that tortoisesvn has something akin to --pin-externals, but haven't
>> figured out if smartsvn has something like that.
> It does. The first version of SmartSVN that migrated off SVNKit to
> JavaHL (from Subversion 1.8) had a two-step process for updating the
> externals. The latest version should be using the atomic pin-externals
> capability.

Cool, thanks for the info. I'm going to set up a couple test projects
and try out externals vs. nested working copies to make sure I
understand the differences.

Grant Edwards               grant.b.edwards        Yow! My EARS are GONE!!
Received on 2016-04-26 20:35:11 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.