From: "Mark A. Greer" <mgreer@mvista.com>
To: Val Henson <val@nmt.edu>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Paul Mackerras <paulus@samba.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: The Plan
Date: Wed, 07 Nov 2001 17:24:41 -0700 [thread overview]
Message-ID: <3BE9D0C9.5E4A3F8@mvista.com> (raw)
In-Reply-To: 20011107134125.O22194@boardwalk
Val Henson wrote:
> 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. :)
Yeah but if you do it the other way, you end up with a directory with a
clutter of subdirs--exchanged one clutter for another.
> What is the problem we're trying to solve here?
Hmmm, clutter I suppose but to be honest I don't have a problem with the way
it is now...
Mark
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-08 0:24 UTC|newest]
Thread overview: 21+ 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
2001-11-08 0:24 ` Mark A. Greer [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-03-24 22:35 David Miller
2009-03-24 22:43 ` Ramkrishna Vepa
2009-03-24 22:48 ` David Miller
2009-03-25 2:03 ` Vlad Yasevich
2009-03-25 2:06 ` David Miller
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=3BE9D0C9.5E4A3F8@mvista.com \
--to=mgreer@mvista.com \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.org \
--cc=val@nmt.edu \
/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.