"hg pull" vs "hg unbundle"

Matt Mackall mpm at selenic.com
Fri Feb 24 12:24:18 CST 2012

On Fri, 2012-02-24 at 19:07 +0100, Pierre-Yves David wrote:
> As highlighted in this issue3266 [1] bundle are not aware of phase. As a
> result:
>     `hg pull` threats them as public repo --> content is public
>     `hg unbundle` threats them as bundle --> content as draft

The default assumption should probably be to treat them as public.

> Question 1:-
>     Are we ok with `hg pull X.hg` doing something else than `hg unbundle X.hg`?

It already does. In particular, pull unpacks the entire bundle into /tmp
for random access. So a bundle of any big project fills the disk and
crashes. It should probably just be short-circuited to unbundle.

> Question 2:
>     If we are ok question 1, shall we warn the user on pull?
> Question 3:
>     How shall we handle phase transfert in the delayed pull usecase?
>     $ hg incoming --bundle X.hg
>     $ hg (pull|unbundle) X.hg
> Question 4:
>     Is there any room for phase is in incoming new bundle format?


Mathematics is the supreme nostalgia of our time.

More information about the Mercurial-devel mailing list