linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-dev@ozlabs.org, Becky Bruce <becky.bruce@freescale.com>,
	linuxppc64-dev@ozlabs.org
Subject: Re: RFC: proposed arch/powerpc directory structure
Date: Wed, 10 Aug 2005 17:35:34 -0400	[thread overview]
Message-ID: <20050810213533.GA2353@tuxdriver.com> (raw)
In-Reply-To: <22fac6c20e1ee142606e4295722c2d1d@embeddededge.com>

On Wed, Aug 10, 2005 at 01:01:34PM -0400, Dan Malek wrote:

> inside of them.  Regardless of the build or management tools we use, I 
> still find it
> nice to keep a concise file name that is still descriptive, and take 
> advantage of
> the directory structure names to assist with this.

I'll second that, fwiw...

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2005-08-10 21:35 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 [this message]
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
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=20050810213533.GA2353@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=becky.bruce@freescale.com \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc64-dev@ozlabs.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).