TK Soh teekaysoh at yahoo.com
Fri Sep 9 01:10:59 CDT 2005

--- Matt Mackall <mpm at selenic.com> wrote:
> The bundle command finds all the changes that are not in the remote
> repo, generates a changegroup identical to the one used in the wire
> protocol, compresses it with bzip2, and writes it into the specified
> file.
> This file can then be transferred with traditional means (email
> attachment, FTP, scp, http, etc.) and will preserve all the changeset
> information for later application with the unbundle command.

I've been trying to fit bundle-unbundle into our development environment, but
so far couldn't really get a good picture worked out. Perhaps you can provide
some hint on the usage pattern with these two commands? FYI, we do cross-site
development, but can only share the work by tranfering the delta/repo through a
central dropbox server, or emails. Unfortunately serving the repo by http will
be relatively troublesome, as it requires root permission. The repo sizes are
usually in terms of hundred MBytes. 

One problem I would foresee is that bundle needs to look at a reference repo to
find the changegroups to generate, and the reference repo would mostly be a
remote one. Of course we may create local references, but this may be an issue
due to the size of our repos, and other overhead in maintaining them.


Click here to donate to the Hurricane Katrina relief effort.

More information about the Mercurial mailing list