Rules for triggering an svn subrepo checkout?

[Jon Marbach]

Hi there - first post here - Mercurial is great! I've been loving it for
years. Thanks in advance...

I've been trying out the subrepos feature for the first time to pull in a
mix of hg and svn repos and I have a few questions that I don't see
answered anywhere else...

1) What are the rules for how mercurial decides to run an svn checkout for
a subrepo? I decided to delete one checked-out subrepo because it had
gotten into an odd state, and I had assumed running some variant of hg
update would re-check it out, but I simply get a message from svn that "XXX
is not a working copy". (For reference, I'm doing this from the command
line on linux using Mercurial ~4.0.) I would have expected hg to behave the
(roughly) the same way that it does when a file goes missing: that an
update -C brings it back.

2) Searching for answers to the above, led to several results which imply
that switching branches with different sets of subrepos won't check out new
svn subrepos. (For example,
https://bz.mercurial-scm.org/show_bug.cgi?id=4427) Can someone confirm what
the expected/actual behavior is? If it's true that hg won't check out new
subrepos when switching revs/branches, then... well, I'll wait for an
answer first.

3) Is there a way to make the svn console i/o interactive so that I can a)
see what it's doing to get a sense of progress b) respond to any prompts
that come up [e.g., password prompts]?

Thanks again,
Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial/attachments/20170404/2b24439a/attachment.html>