From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Drew Northup <drew.northup@maine.edu>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Miles Bader <miles@gnu.org>,
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>
Subject: [1.8.0] Re: reorganize the mess that the source tree has become
Date: Sat, 5 Feb 2011 16:11:43 +0100 [thread overview]
Message-ID: <20110205151143.GA14187@vidovic> (raw)
In-Reply-To: <1296859660.1255.49.camel@drew-northup.unet.maine.edu>
The 04/02/11, Drew Northup wrote:
> Having once upon a time (in CVS days) taken over a project that was
> neatly organized into tons of folders I can say that more folders is not
> always better.
> If you are organizing things into modules by folders, and those things
> are mutually exclusive pre-compilation then doing so may make sense. If
> the folders ADD value to the project by adding organization--as opposed
> to hiding disorganization--then they may have value.
This _is_ what we are talking about. Not tons of folders or whathever
you might think.
> destructive things
> killed that first
> project
> project exploded with a fury resembling
> a religious confrontation. see that happen to Git
> see that project die you exasperate
> enough of the core developers
Read again. I'm pretty sure this was not your goal but this almostly
looks like FUD to me. So, I don't think I'll involve to more discussion
in this subthread.
--
Nicolas Sebrecht
prev parent reply other threads:[~2011-02-05 15:12 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 ` [1.8.0] " Nicolas Sebrecht
2011-02-04 22:47 ` Drew Northup
2011-02-05 15:11 ` Nicolas Sebrecht [this message]
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=20110205151143.GA14187@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=drew.northup@maine.edu \
--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 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.