On 2016-04-26, Branko Čibej <br...@apache.org> wrote:
> 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.
Yea, I can't really imagine any advantage to the "non-externals"
method except you don't have the opportunaty to accidentally tag a
version with an externals link pointing to wherever@HEAD and then
check it out later and build something incorrectly without realizing
what happened.
Both approches require people to follow some new workflow rules, but
the externals route seems to require fewer.
--
Grant Edwards grant.b.edwards Yow! Didn't I buy a 1951
at Packard from you last March
gmail.com in Cairo?
