From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com, Elena Zannoni <ezannoni@redhat.com>,
Eli Zaretskii <eliz@is.elta.co.il>
Subject: Re: New directory src/gdb/misc?
Date: Thu, 07 Mar 2002 10:44:00 -0000 [thread overview]
Message-ID: <20020307134457.B13922@nevyn.them.org> (raw)
In-Reply-To: <3C878E6B.9000704@cygnus.com>
On Thu, Mar 07, 2002 at 10:59:39AM -0500, Andrew Cagney wrote:
> Is the right direction to split things across ``functional'' (utils,
> nat, isa/abi, ..) lines rather than ``usage'' (common to gdb/gdbserver,
> commont to gdb/sim, ...) lines? A functional split would result in
> gdbserver cherry picking from random directories the bits it wants from
> core gdb.
One type of directory seem particularly useful:
- directories in which each file serves the exact same purpose for a
different target. However many of these we want, though the more
pieces it goes into the more complicated it'll be to figure out what
does what...
The other useful idea would be purely organizational (like breaking up
utils).
Both of these require creating subdirectories; I think both may be good
ideas.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-07 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 18:31 Andrew Cagney
2002-03-06 21:31 ` Daniel Jacobowitz
2002-03-06 22:13 ` Eli Zaretskii
2002-03-06 22:31 ` Andrew Cagney
2002-03-07 6:55 ` Elena Zannoni
2002-03-07 7:59 ` Andrew Cagney
2002-03-07 10:44 ` Daniel Jacobowitz [this message]
2002-03-06 22:22 ` Andrew Cagney
2002-03-07 10:42 ` Daniel Jacobowitz
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=20020307134457.B13922@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=ezannoni@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