From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: <cpu>-frame.c, frame/<cpu>.c, config/<cpu>/frame.c, ...
Date: Sun, 04 May 2003 15:44:00 -0000 [thread overview]
Message-ID: <20030504154404.GB12099@nevyn.them.org> (raw)
In-Reply-To: <3EB48526.9060104@redhat.com>
On Sat, May 03, 2003 at 11:12:38PM -0400, Andrew Cagney wrote:
> This picks up an old old topic
>
> Since MarkK is threatening to get the i386 using the new frame code, now
> is probably the time to think about where all these frame modules should
> live:
>
> d10v-frame.[hc]:
> Fills the top-level directory up with more stuff. That got objections
> when it was last suggested.
>
> frame/<cpu>.[hc]:
> Keeps all the frame code in one directory. This makes it clearer that
> the code is ment to be frame centric (and not the place to put non-frame
> stuff).
>
> config/<cpu>/frame.[hc]:
> Keeps the cpu stuff in a single directory.
Like I said last time, I'm in favor of config/<cpu>/. Splitting
support files for a particular CPU across multiple functional area
directories would be annoying, I think. The toplevel directory could
do with some pruning. And I don't think it will be especially
confusing.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-04 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 3:12 Andrew Cagney
2003-05-04 3:33 ` Doug Evans
2003-05-04 4:10 ` Andrew Cagney
2003-05-04 7:31 ` Doug Evans
2003-05-04 15:46 ` Daniel Jacobowitz
2003-05-04 16:42 ` Andrew Cagney
2003-05-04 18:25 ` Daniel Jacobowitz
2003-05-07 18:49 ` Andrew Cagney
2003-05-04 15:44 ` Daniel Jacobowitz [this message]
2003-05-04 16:41 ` David Carlton
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=20030504154404.GB12099@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).