News for hackers. Stuff that matters.
Re:Mercurial 2.8 Released by taeric on Tuesday November 05, 2013 @07:21PM (#6679604)
The kernel argument still jumps out at me, though. There are many "subsystems" to the kernel that could have easily been split to separate repositories had that been the idea for the project. Indeed, this seems to be the entire monolithic kernel debate. They do not split things out, even if they could potentially do so.

Now, in general I think I agree with your points. Your two specific points I specifically promote at work and on school projects.

And, I fully see how the large organizations you are referring to would hit this. Especially when they essentially have independent projects in development. What I do not understand is where that line is drawn. To the point that I often find myself on the counter argument at work when teams want to immediately start a project in 3 repositories because we may want some utilities used elsewhere.

Take gnome. At face value, it seems like most of the core of gnome could be in one repository. Instead, it is very highly split out and has a specialized build system to support the it. Was this strictly necessary? Or is this more to support other infrastructure ideas at play? (This make sense?)

There are no comments on this comment yet.