cloning with subrepos to an ssh url

Snidely snidely.too at gmail.com
Wed Aug 17 19:02:48 UTC 2011



On Aug 17, 11:32 am, Kevin Bullock <kbullock+mercur... at ringworld.org>
wrote:
> On Aug 17, 2011, at 8:55 AM, Julius Ziegler wrote:
> > Having no working copy is actually the first thing that puzzles me,
> > but this also happens if I do not have any suprepos.
>
> When you're cloning a _local_ repo to a _remote_ location, the assumption
> is that you're either creating a central 'canonical' repository,
> or making a backup copy. In either case, you don't need (nor likely want)
> a remote working copy.
>
> Now note that cloning and pushing don't propagate subrepos; update does,
> because in order to know what subrepos at what revisions should be present
> in the outer repo, hg has to read the .hgsub and .hgsubstate files
> from the _working copy_ (at a particular checked-out revision).
>
> Thus, when you clone local->remote, since the update step is skipped,
> the subrepos aren't cloned along with the outer repo.


So is the fix to do a 2nd "hg upate"?  Or some other step?  Or is
there no way to subrepos to a remote target?

/dps



More information about the Mercurial mailing list