On Mon, 31 Jan 2011, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxxxxxx> writes: > > > 1) Create a src/ directory and move *.c, *.h, *.sh, *.perl, *.py and > > the builtin directory from the root directory to it. > > > > 2) Create a build/ directory, or bin/ if prefered, to hold the result of > > the build. > >... > > 6) And fix up all the Makefiles to cope with the above movements. > > > > What do you think? > > Knee-jerk reaction: not very motivated to make the top-level directory > just a skeleton that holds various directories with a handful of > administrative files like Makefile, README, etc. Under your proposal, the > bulk of the current content at the top would simply move to another single > directory anyway, so I don't immediately see much point of such a move, > other than adding merge burden on me and rebase burden on others, that > is. I really think that the top directory is not the proper place for source files to live, especially considering how big a project Git is now. The top directory should be like a table of content and not the content itself. But if you the maintainer doesn't see a long-term value in this to be greater than the one-time burden, then I'm afraid there's nothing I can do to help it. > But that is just a knee-jerk reaction, just to fill the "Risks:" section > you didn't fill. Your missing "Migration Plans" section might outline a > clever approach to lessen the interim hurt while merging in-flight topics. Well, there is no such plan. Given that 1.8 is meant to be an inflexion point for users, it could as well be for developers the best time to clean up this mess too. Nicolas -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html