From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb@sources.redhat.com
Subject: Re: Who owns gdbserver?
Date: Wed, 27 Jun 2001 21:26:00 -0000 [thread overview]
Message-ID: <3B3AB1DF.9020500@cygnus.com> (raw)
In-Reply-To: <20010622090351.A14790@nevyn.them.org>
> My current inclination is that, after we enumerate precisely what
> interfaces are needed, we may need to break some of the nat and tdep
> files up into smaller pieces, so that gdbserver can link in the parts
> it really needs - and the parts it can reasonably include the support
> code for.
Sounds good in theory, there is a catch-22 though. Doing any cleanup is
a lot easier with everything multi-arch.
I'm happy for, short term, there to be a slightly bloated GDBserver, if
it means that people concentrate more on getting things multi-arched.
Andrew
next prev parent reply other threads:[~2001-06-27 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 13:30 John S. Kallal
2001-06-22 8:42 ` Andrew Cagney
2001-06-22 9:04 ` Daniel Jacobowitz
2001-06-27 21:26 ` Andrew Cagney [this message]
2001-06-28 7:41 ` Quality Quorum
-- strict thread matches above, loose matches on Subject: below --
2001-06-20 22:12 Daniel Jacobowitz
2001-06-21 12:40 ` J.T. Conklin
2001-06-22 8:28 ` Andrew Cagney
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=3B3AB1DF.9020500@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--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