Binary files in exported changesets

[Eric Hopper]

On Fri, Apr 21, 2006 at 12:55:13PM +1000, Michael Smith wrote:
> Am I wrong about this? Is the file encoded or escaped in a way that I
> haven't recognised? Or should I be really careful about what I do with
> exported changesets? My mail system encodes the changeset as base64
> anyway so it should get to the other end unchanged, but I can't see
> this working if the changeset is sent inline in a mail message.

export is not the best way to do this.  There is no good standard binary
changeset format at this point.  And export is more for reviews and
moving data between different SCMs, not for moving things between
Mercurial repositories.

What you really should be using is 'bundle'.  Bundle's two big downsides
are that they are not human readable, and they only work for copying
changesets between Mercurial repositories.  The big advantages are that
they're smaller than exports, work better in general, handle binary
files just fine, and keep the changeset histories related in a more
sensible way.

Have fun (if at all possible),
-- 
"It does me no injury for my neighbor to say there are twenty gods or no God.
It neither picks my pocket nor breaks my leg."  --- Thomas Jefferson
"Go to Heaven for the climate, Hell for the company."  -- Mark Twain
-- Eric Hopper (http://www.omnifarious.org/~hopper) --
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20060421/83a6e0a7/attachment-0001.asc>