Update fails after pulling from a non default path that has modified subrepos

Mads Kiilerich mads at kiilerich.com
Fri Sep 21 05:08:08 CDT 2012

On 09/21/2012 11:04 AM, Angel Ezquerra wrote:
> Hi,
> When you have subrepos on your repository, running pull on the top
> repository does not pull changes from its subrepos. Instead subrepos
> are pulled "as needed" when you update to the corresponding parent
> repository revisions.
> This causes a problem if you ever pull from a non default path,
> because hg update uses the defautl path when pulling subrepos. As far
> as I know there is no way to tell hg update to use a different pull
> source,

There is - see http://mercurial.selenic.com/wiki/Subrepository#Update .

> nor to tell hg pull to pull all subrepos.

See the advice in http://mercurial.selenic.com/wiki/Subrepository#Pull 
and always use --update.

The best solution is of course to not use subrepos.


More information about the Mercurial-devel mailing list