HG bundle file size

[Matt Mackall]

On Tue, 2014-08-05 at 22:02 +1200, Sebastian Unger wrote:
> Hi there,
> 
> I'm not sure whether this should be directed here or the developer list.
> Let me know if I should take this over there.
> 
> I am a bit confused about the size of the files generated with the hg
> bundle command. I often use those to transfer or store changesets that I'm
> not prepared to push for various reasons. These files seem extraordinarily
> large to me. For instance, in the case I'm looking at right now, I'm trying
> to bundle up 4 changesets with a couple one-line changes each. The
> changesets I want are in draft, everything else is public. For comparison I
> also export the same changesets and pass the resulting diff through bz:
> 
> 
> 
> 
> 
> 
> 
> 
> *seb at eragon:~/Documents/TTDE/TerminalsRoot$ hg bundle -r 'draft()' --base
> 'public()' bundled.hg4 changesets
> foundseb at eragon:~/Documents/TTDE/TerminalsRoot$ hg export -r 'draft()' |
> bzip2 -c >bundled.diff.bz2seb at eragon:~/Documents/TTDE/TerminalsRoot$ ls
> -ltotal 208-rw-r--r-- 1 seb users   1700 Aug  5 21:58
> bundled.diff.bz2-rw-r--r-- 1 seb users 206878 Aug  5 21:57 bundled.hg*
> I thought that an export stores most of the info in a bundle (So far I only
> found grafts can't be imported with --exact) and in fact more than a bundle
> (diffs have lots of context that is not needed in a bundle).
> 
> Am I missing something here?

Yeah, this shouldn't happen.

Sure one of those "diffs" doesn't contain a line like "Binary file foo
has changed"?

If you can't share your bundle with us, you can use 'hg bundle --type
none' to get an uncompressed bundle that you can more easily inspect
(for instance with 'strings').

-- 
Mathematics is the supreme nostalgia of our time.