On 26.04.2016 20:32, Grant Edwards wrote: > On 2016-04-26, Branko Čibej <br...@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.
Externals /are/ nested working copies as far as the client is concerned. Sure nothing prevents you from using nested working copies that aren't tracked as externals, but you'll have to invent your own tooling for checkouts, updates, commits, etc. -- Brane
