Re: [1.8.0] reorganize the mess that the source tree has become

From: Erik Faye-Lund <kusmabite@gmail.com>
Date: Feb 4, 2011, 11:17 UTC
Message-ID: <AANLkTinFHs=sgcPSAdPMrCORpzTO7no-6CqUi_9AFzXQ@mail.gmail.com>
In-Reply-To: <87bp2sy2mf.fsf@catnip.gol.com>

On Fri, Feb 4, 2011 at 3:06 AM, Miles Bader <miles@gnu.org> wrote:

Show 12 quoted lines

> Hilco Wijbenga <hilco.wijbenga@gmail.com> writes:
>> Quite frankly, I'm surprised there are (presumably experienced)
>> developers who do not immediately see the value of a little
>> organization. Surely, given the use of code conventions, formatting
>> rules, etcetera, the obvious one step further is to also organize
>> where the files go?
>
> I think one of the problems is that what's been suggested seems like
> window-dressing.  Moving everything into src/ and calling it "organized"
> doesn't actually accomplish much other than perhaps making the README
> file more visible to newbs; things are _still_ a mess, just a mess with
> four more letters...

FWIW, I don't quite see what's wrong with "window dressing" here. Making those files more visible is a good thing, IMO.

But I'm not so sure I agree that the rest of the source tree is such a mess that everyone makes it out to be. OK, there's a lot of source-files on the top-level (which would be the src-level with this change), but why is that such a bad thing? And if this is a big deal, perhaps moving libgit-sources to a separate folder would help?