From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com, mrg@redhat.com
Subject: Re: [patch/rfc] Don't assume the host
Date: Sun, 20 Jan 2002 10:55:00 -0000 [thread overview]
Message-ID: <2561-Sun20Jan2002205223+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <3C4B0EA1.90403@cygnus.com> (message from Andrew Cagney on Sun, 20 Jan 2002 13:38:25 -0500)
> Date: Sun, 20 Jan 2002 13:38:25 -0500
> From: Andrew Cagney <ac131313@cygnus.com>
> >
> > The way I see it, "Porting GDB" is a cookbook: it should list the
> > necessary steps without explaining their rationale too much. It
> > should refer to "Host Definition" for more info, wherever appropriate.
> > "Host Definition", by contrast, should explain as much as possible
> > each of the components of the host definition machinery.
>
> Ah, ok. Yes, that makes sense. Should ``Porting GDB'' be moved to
> before the host, architecture and target sections (and add a native
> section?). That way the user is lead into the other chapters. Porting
> GDB being a brief overview.
Yes, if we say in ``Porting GDB'' that it's an overview, and the other
chapters describe the stuff in more details, it would make a lot of
sense to move ``Porting GDB''.
prev parent reply other threads:[~2002-01-20 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 20:44 Andrew Cagney
2002-01-18 13:56 ` Andrew Cagney
2002-01-20 0:29 ` Eli Zaretskii
2002-01-20 9:13 ` Andrew Cagney
2002-01-20 10:21 ` Andrew Cagney
2002-01-20 10:25 ` Eli Zaretskii
2002-01-20 10:38 ` Andrew Cagney
2002-01-20 10:55 ` Eli Zaretskii [this message]
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=2561-Sun20Jan2002205223+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mrg@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