News for hackers. Stuff that matters.
Re:Mercurial 4.0 Sprint Notes by hinkley on Tuesday October 18, 2016 @03:27PM (#12737846)
The big thing I miss about Subversion is that you could check out one subtree. On the biggest SVN project I worked on, we built 5 binaries from the same code tree, but only the leads and a couple of senior devs that worked on crosscutting concerns (ie, the people who would do the mass edits you mention) had the entire tree checked out. Everyone else had just the one or two modules they were working on.

The second biggest, we used just enough of a module system to enforce modularity by having a single code repo but separate compilation units. Your circular dependencies between subprojects would show up at compile time (or at least, on a clean build, as our CI machine did). Stopped a lot of obscure runtime issues and made people think about what they were trying to do.

Re:Mercurial 4.0 Sprint Notes by tux1968 on Tuesday October 18, 2016 @04:35PM (#12738413)
This post is about Mercurial with which i'm not familiar, but in Git you can checkout a subtree since version 1.7[1]. It's commonly called "sparse checkout".

[1] http://jasonkarns.com/blog/subdirectory-checkouts-with-git-s...

Re:Mercurial 4.0 Sprint Notes by glandium on Tuesday October 18, 2016 @06:22PM (#12739260)
But you still need to clone the whole thing. Sparse clones are theoretically possible, but aren't implemented AFAIK.
Re:Mercurial 4.0 Sprint Notes by emmelaich on Tuesday October 18, 2016 @08:41PM (#12740017)
You can do a shallow clone; see the --depth option.
Re:Mercurial 4.0 Sprint Notes by glandium on Tuesday October 18, 2016 @10:54PM (#12740648)
That reduces the history depth, but still gets the whole tree. Arguably, the history is much more interesting than having the entirety of the monorepo for many people.