https://bz.mercurial-scm.org/show_bug.cgi?id=6951
Bug ID: 6951
Summary: remotefilelog without history
Product: Mercurial
Version: 6.8.1
Hardware: PC
OS: NetBSD
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: mercurial-bugzi...@campbell.mumble.net
CC: mercurial-de...@mercurial-scm.org
Python Version: ---
With remotefilelog enabled (and
https://bz.mercurial-scm.org/show_bug.cgi?id=6936 and
https://bz.mercurial-scm.org/show_bug.cgi?id=6937 worked around by setting
remotefilelog.getfilestype=threaded, remotefilelog.excludepattern=.hgtags), a
shallow clone of (a repository more or less equivalent to)
https://anonhg.NetBSD.org/src weighs in at about 300 megabytes.
If I use a narrow clone limited to a few directories (bin/sh, bin/test,
bin/kill, usr.bin/printf, lib/libedit, lib/libterminfo), or a narrow shallow
clone, it's about the same, plus or minus a few megabytes.
In contrast, a git sparse-checkout of the same subdirectories, in a shallow
treeless (--filter=tree:0) clone of a corresponding repository conversion,
weighs in at about 30 MB.
Are there other options for slimming down the local storage needed by shallow
and/or narrow clones? If not, what hard technical problems -- versus simple
matters of programming (and testing) -- lie in the way?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel
