while i like LargeFiles, it's really not enough. Support for binary content (and indeed, history truncation) needs to be native. As it stands, LargeFiles can only be used on intranet networks, and if you've ever used it for any serious purpose, you'll run into corruption.

It's really disappointing to see 3.0 announced with no solution to this.

FYI Mercurial has time-based releases. So 3.0 doesn't mean anything special (it's just the next feature release after 2.9).

http://mercurial.selenic.com/wiki/TimeBasedReleasePlan

Why intranet only? The data still comes from the HG server through standard means.

And what kind of data corruption do you see? It tracks files by their SHA1 value and downloads them as needed. Did you report any corruption issues you hit? Or have links to anything specific?

Largefiles are being used for production in game companies and we have not gotten reports about corruption.

i used large files with game assets via tortoise hg. if there's a network timeout, corruption of the largefiles occurs ..

what client do you use?