SV: Bundle and rev

Yuya Nishihara yuya at tcha.org
Tue Mar 7 14:25:04 UTC 2017


On Tue, 7 Mar 2017 11:02:28 +0000, Lars wrote:
> Thanks for your response.
> 
> > --rev can be used to limit the head revisions to be included in the bundle
> > file. For example, if the destination repo has changes up to rev.1 and you
> > do "hg bundle --rev 2", only rev.2 will be included in the bundle.
> 
> >   -- 1 -- 2
> >       \
> >        - 3
> 
> Running the command "hg bundle --rev 2 file.hg" in a few repositories all produce the error message "searching for changes. no changs found". In our setup this command does not appear to work as you describe. Any thoughts?

That's probably because your peer repo contains the revision 2. Try with
"--base null" option for example.

> > If --all specified, hg assumes the destination repo has no revision, so
> > "hg bundle --rev 2 --all" will include rev.1 and 2. --base specifies the
> > revisions which can be excluded from the bundle file.
> 
> In other words using the --all switch will negate the --rev switch?

No. --all disables the outgoing discovery, which is practically the same as
setting "--base null". "hg bundle" is very similar to "hg push", in which it
generates a bundle that contains the minimal changesets needed by the peer
repository.



More information about the Mercurial mailing list