From: Val Henson <val@nmt.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: The Plan
Date: Wed, 7 Nov 2001 13:41:25 -0700 [thread overview]
Message-ID: <20011107134125.O22194@boardwalk> (raw)
In-Reply-To: <Pine.GSO.4.21.0111071246050.11631-100000@mullein.sonytel.be>; from geert@linux-m68k.org on Wed, Nov 07, 2001 at 12:47:33PM +0100
On Wed, Nov 07, 2001 at 12:47:33PM +0100, Geert Uytterhoeven wrote:
>
> On Wed, 7 Nov 2001, Paul Mackerras wrote:
> > - Files which relate only to one platform, or a small number of
> > platforms, move to arch/ppc/platforms. (There are some minor
> > exceptions to this rule which we can discuss if people are
> > concerned.) We end up with:
>
> Why not move platform-specific files to arch/ppc/<platform>/ instead?
>
> Your solution reduces the clutter only by a factor of 2, while creating
> platform-specific directories reduces it by a factor of n.
I agree with Geert. I don't think that dividing the clutter into two
directories instead of one really improves matters. Each directory is
still monstrously huge and the division is non-obvious.
arch/ppc/masochist would be easier to understand. :)
What is the problem we're trying to solve here?
-VAL
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-07 20:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 11:35 The Plan Paul Mackerras
2001-11-07 11:47 ` Geert Uytterhoeven
2001-11-07 11:50 ` Paul Mackerras
2001-11-07 22:19 ` Frank Rowand
2001-11-07 20:41 ` Val Henson [this message]
2001-11-08 0:24 ` Mark A. Greer
2001-11-08 0:26 ` Mark A. Greer
2001-11-07 12:09 ` Matt Porter
2001-11-07 17:44 ` Mark A. Greer
2001-11-08 0:41 ` Mark A. Greer
2001-11-08 2:51 ` Paul Mackerras
2001-11-08 19:08 ` Mark A. Greer
2001-11-08 0:48 ` Mark A. Greer
2001-11-08 1:12 ` Tom Rini
2001-11-08 11:14 ` Chris Emerson
2001-11-08 12:07 ` Geert Uytterhoeven
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=20011107134125.O22194@boardwalk \
--to=val@nmt.edu \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
/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).