On Sun, Jun 21, 2020 at 11:33 AM Mayuresh <mayur...@acm.org> wrote: > > On Sat, Jun 20, 2020 at 11:35:53AM +0530, Mayuresh wrote: > > On Fri, Jun 19, 2020 at 10:01:35PM -0700, Greg A. Woods wrote: > > > (c) modern change tracking tools try to track changes to whole sets of > > > files at once, so if you have lots of files, and lots of history, > > > this combinatorial problem can sometimes bite at a bad time for the > > > user of a tool trying to manage it all. > > > > In one of the talks by Linus on git I heard him recommending breaking very > > large repositories into some smaller units to get better performance. > > > > Would it be something feasible in NetBSD? A single user requires > > approximately what % of code from what he or she checks out to be actually > > compiled and can there be 1 core and several optional repositories that > > would increase this percentage. > > Just quoting the correct reference[1]: > > <quote> > the way git works (tracking whole trees at a time, never single files), > that ends up being very painful, because it's an "all or nothing" > approach. > > So I'm hoping that if you guys are seriously considering git, you'd also > split up the KDE repository so that it's not one single huge one, but with > multiple smaller repositories > </quote> > > I think, before we adopt a centralized repository (whether hg or git) this > needs to be thought through. > > FreeBSD has been there done that when adopting SVN[2],[3] > > [1] https://lwn.net/Articles/246381/ > [2] https://wiki.freebsd.org/VCSWhy > [3] https://wiki.freebsd.org/GitDrawbacks
This is out of date. FreeBSD is moving to git.