From: Becky Bruce <becky.bruce@freescale.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Thu, 11 Aug 2005 17:41:36 -0500 [thread overview]
Message-ID: <e14ba87891c3c976056fe2bac0e1ef19@freescale.com> (raw)
In-Reply-To: <20050811201821.GY3187@smtp.west.cox.net>
>
>>> I don't like the idea of sticking subdirs in classic32/ either, but
>>> also
>>> can't think of a better name for the catchall of 7xx and 74xx boards.
>>
>> I dont think we where planning on subdirs in classic32.
>
> I took "may collapse into classic 32 at some point" to mean "move into
> classic32/ at some point", for some reason. collapsing the content
> into
> classic32/ will bring us back to the bad-old-days of everything in
> platforms/ (or kernel/).
My apologies - this wasn't at all clear in the proposal. The plan at
present is to not have subdirs under classic32. By "collapsing into
classic32", I meant a move to a more common code base, not a wholescale
copy of the existing files into classic32.
Cheers,
-B
next prev parent reply other threads:[~2005-08-11 22:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 16:45 RFC: proposed arch/powerpc directory structure Becky Bruce
2005-08-10 17:01 ` Dan Malek
2005-08-10 21:35 ` John W. Linville
2005-08-11 0:09 ` Stephen Rothwell
2005-08-11 1:10 ` Olof Johansson
2005-08-11 19:59 ` Tom Rini
2005-08-11 20:13 ` Kumar Gala
2005-08-11 20:18 ` Tom Rini
2005-08-11 22:41 ` Becky Bruce [this message]
2005-08-11 23:07 ` Kumar Gala
2005-08-11 23:19 ` Tom Rini
2005-08-12 2:34 ` Kumar Gala
2005-08-12 3:38 ` Tom Rini
2005-08-11 23:29 ` Dan Malek
2005-08-12 2:09 ` Josh Boyer
2005-08-12 3:49 ` Paul Mackerras
2005-08-12 4:14 ` Tom Rini
2005-08-15 18:25 ` Segher Boessenkool
2005-08-11 20:25 ` Olaf Hering
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=e14ba87891c3c976056fe2bac0e1ef19@freescale.com \
--to=becky.bruce@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).