From: Nguyen Thai Ngoc Duy Date: Fri, 18 Feb 2011 12:33:27 GMT Subject: Re: [RFC/PATCH 0/3] Thinning the git toplevel directory Message-ID: In-Reply-To: <20110218092518.GB30648@elie> On Fri, Feb 18, 2011 at 4:25 PM, Jonathan Nieder wrote: > Changes since the series sent to the list: > ... >  - renamed nonbuiltin/ to commands/.  Names like >   commands/add--interactive.perl even seem to make a kind of sense. I suggest cmds/ to avoid tab-completion conflict with compat. >  - moved the http support mini-library to http/. Move them to commands/ as well? >  - renamed git_remote_helpers to python/, though I'm not very happy >   about that. It don't like having "perl" and "python" directories (makes me thing what if another language appears). If they are just bindings (python dir may not be), how about "bindings" directory and throw them all flat in there? > This is all very off-the-cuff.  I'd be happy for others to pick this > up and remold it to their taste (after all, I'm too used to the > current layout to remember what matters).  It doesn't feel cooked yet. A few more things: - I like the fact that you leave only git.c in topdir. Straight entry point for newcomers. - On the same topic of newcomers, should we pull Documentation/technical out to topdir? A symlink is OK. - test-programs should be still in t/ though. I'm not an advocate for deep layout, but it makes sense to me to keep test programs close to test scripts. - perhaps we can merge block-sha1 and ppc into one? We can rename ppc/sha1.* to sha1/ppc-sha1.* - I agree with Jeff that generated files should stay in the same place with source files. Although I tend to use "git ls", untracked files do not bother me much ;-) -- Duy