From: Miles Bader <miles@gnu.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: George Spelvin <linux@horizon.com>, git@vger.kernel.org
Subject: Re: [1.8.0] reorganize the mess that the source tree has become
Date: Thu, 03 Feb 2011 17:09:00 +0900 [thread overview]
Message-ID: <buo39o535gj.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1102030036420.12104@xanadu.home> (Nicolas Pitre's message of "Thu, 03 Feb 2011 01:16:10 -0500 (EST)")
Nicolas Pitre <nico@fluxnic.net> writes:
>> But just moving the whole existing pile into a subdirectory "because
>> everyone else does it" is not a reason; that's superstition.
>
> There is no superstition here, simply basic elegance.
"basic elegance" is hardly well-defined, and although there are probably
issues on which there's general agreement, this doesn't appear to be one
of them.
>> Having to type "src/" a lot more often is definitely a downside.
>
> Come on. This is a rather egocentric argument without much substance.
It certainly has more substance than hand-waving like "basic elegance"
though...
Some slightly more concrete arguments have been:
Pro-src: Big top-level dir scares newbs
Anti-src: Extra typing is annoying
I'm not really against a "src/" subdir, but it seems mostly a matter of
taste, and I've seen plenty of projects where the src/ directory seemed
pretty pointless...
-Miles
--
Politics, n. A strife of interests masquerading as a contest of
principles. The conduct of public affairs for private advantage.
next prev parent reply other threads:[~2011-02-03 8:09 UTC|newest]
Thread overview: 42+ 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 [this message]
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 ` [1.8.0] " Nicolas Sebrecht
2011-02-04 22:47 ` Drew Northup
2011-02-05 15:11 ` Nicolas Sebrecht
-- strict thread matches above, loose matches on Subject: below --
2011-01-31 5:53 What's cooking in git.git (Jan 2011, #06; Sun, 30) Junio C Hamano
2011-01-31 17:05 ` Planning for 1.7.5 and 1.8.0 Junio C Hamano
2011-01-31 20:28 ` [1.8.0] reorganize the mess that the source tree has become Nicolas Pitre
2011-01-31 20:57 ` Junio C Hamano
2011-01-31 21:08 ` Matthieu Moy
2011-01-31 21:33 ` Nicolas Pitre
2011-01-31 21:19 ` Nicolas Pitre
2011-01-31 21:00 ` Jeff King
2011-01-31 21:28 ` Nicolas Pitre
2011-01-31 22:17 ` Junio C Hamano
2011-01-31 22:36 ` João P. Sampaio
2011-01-31 22:37 ` Nicolas Pitre
2011-01-31 23:12 ` Jeff King
2011-02-01 0:29 ` Nicolas Pitre
2011-02-01 1:48 ` Jeff King
2011-02-01 4:05 ` Nicolas Pitre
2011-02-01 12:42 ` Thomas Rast
2011-02-01 11:14 ` Jonathan Nieder
2011-02-01 11:22 ` Jonathan Nieder
2011-02-01 13:08 ` Nicolas Pitre
2011-02-01 16:02 ` Nguyen Thai Ngoc Duy
2011-02-01 21:53 ` Junio C Hamano
2011-02-01 0:35 ` Erik Faye-Lund
2011-02-01 1:53 ` Jeff King
2011-02-01 1:00 ` Sverre Rabbelier
2011-02-01 1:57 ` Jeff King
2011-02-01 7:24 ` Jay Soffian
2011-02-01 14:42 ` Andreas Ericsson
2011-02-05 3:21 ` Martin von Zweigbergk
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=buo39o535gj.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.