News for hackers. Stuff that matters.
Re:On Monolithic Repositories by qznc on Wednesday August 05, 2015 @04:03AM (#10008465)
Facebook uses Mercurial. Mercurial works well for small projects as well.

Mercurial has no clear technical advantage over git though. That might change if Mercurial gets narrow clones (only check out subdirectories) working and git fails to clone (haha) that.

Re:On Monolithic Repositories by glandium on Wednesday August 05, 2015 @04:29AM (#10008537)
IIRC there were experimental patches implementing it for git a few months ago.

Ironically, to make narrow clones happen, Mercurial is going to change its internal structure representing the files in the repository (the manifest) to use a separate manifest for each sub-directory... like git has been doing for trees from day one.

Re:On Monolithic Repositories by qznc on Wednesday August 05, 2015 @04:50AM (#10008582)
I found patches from 2008, but nothing recent.

http://article.gmane.org/gmane.comp.version-control.git/9634...

Re:On Monolithic Repositories by glandium on Wednesday August 05, 2015 @05:00AM (#10008617)
Your link is about narrow checkout, not narrow clone (so the .git data is still transfered completely, as opposed to transfered partially). Maybe what I'm thinking about was just a discussion with no formal patch, I don't remember.
Re:On Monolithic Repositories by davvid on Wednesday August 05, 2015 @06:49AM (#10008885)
The two features of interest are "shallow clone" and "partial checkout".

Both of these features are already part of git.

A current experiment is an untracked files cache, which speeds up stuff on large repos considerably. This stuff is actively being worked on -- the git project has always valued performance.

Re:On Monolithic Repositories by qznc on Wednesday August 05, 2015 @07:22AM (#10008970)
No, "shallow clone" and "partial checkout" are both different to "narrow clone". Maybe "partial clone" would fit the git terminology better.

A shallow clone misses history after a certain point in time (well, commit order). A narrow clone misses history except in a subtree. A partial clone looks like a narrow clone in the workspace, but a narrow clone should have substantially less objects to download and store.