Can anything be done about the large files problem?

Andi McClure andi.m.mcclure at gmail.com
Sat Nov 11 20:00:13 UTC 2017


 So, to keep this brief: I really like Mercurial and I really, really hate
Git, but I’m about to switch from Mercurial to Git for the sole reason that
I am starting a project which will have many large, frequently-changing
binary files, and Git has a solution for this (LFS), and Mercurial in
practice does not. Mercurial has the largefiles extension, but since
Bitbucket does not support it, largefiles may as well not exist. For me and
I suspect many other developers, paid VCS hosting is an option, but
self-hosting is just plain not.

Can anything be done about this? Does the Mercurial community have a
timeline for any solution to the large files problem? I don’t think I’m the
only user Mercurial is losing over this; a solution for large files is
basically necessary in (for just one example) game dev.

I do notice this page proposing Mercurial support for the git LFS protocol
exists on the wiki: [ https://www.mercurial-scm.org/wiki/LfsPlan ] and is
being regularly updated, but that page does not make clear either the
intended timeline, or whether or not Bitbucket is on board (would Bitbucket
*need* to be on board?). Does anyone know, if I’m interested in taking
advantage of the “LFS plan” described there, when that will be practically
possible (assuming part of what I consider "practically possible" is
support by a hosting provider I can trust as much as I trust Bitbucket or
Github)?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial/attachments/20171111/1c6696ac/attachment.html>


More information about the Mercurial mailing list