From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Miles Bader <miles@gnu.org>
Cc: Hilco Wijbenga <hilco.wijbenga@gmail.com>,
git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>,
George Spelvin <linux@horizon.com>,
Eugene Sajine <euguess@gmail.com>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: [1.8.0] Re: reorganize the mess that the source tree has become
Date: Fri, 4 Feb 2011 19:15:50 +0100 [thread overview]
Message-ID: <20110204181550.GA14173@vidovic> (raw)
In-Reply-To: <87bp2sy2mf.fsf@catnip.gol.com>
The 04/02/11, Miles Bader wrote:
> 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...
So it would be an ordered mess, at least. The current amount of files in
the root directory do make things harder for people not already familiar
with the content. FMHO, moving the source files into a subdirectory
could be only a first step to the good direction.
--
Nicolas Sebrecht
next prev parent reply other threads:[~2011-02-04 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 2:29 [1.8.0] reorganize the mess that the source tree has become George Spelvin
2011-02-02 8:31 ` Erik Faye-Lund
2011-02-02 20:01 ` Pascal Obry
2011-02-03 6:16 ` Nicolas Pitre
2011-02-03 8:09 ` Miles Bader
2011-02-03 18:01 ` Andreas Schwab
2011-02-03 18:46 ` Eugene Sajine
2011-02-03 21:42 ` Hilco Wijbenga
2011-02-04 2:06 ` Miles Bader
2011-02-04 8:30 ` Tor Arntsen
2011-02-04 10:49 ` Jakub Narebski
2011-02-04 11:17 ` Erik Faye-Lund
2011-02-04 18:15 ` Nicolas Sebrecht [this message]
2011-02-04 22:47 ` [1.8.0] " Drew Northup
2011-02-05 15:11 ` Nicolas Sebrecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110204181550.GA14173@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=hilco.wijbenga@gmail.com \
--cc=linux@horizon.com \
--cc=miles@gnu.org \
--cc=nico@fluxnic.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).