From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sje@cup.hp.com, gdb-patches@gcc.gnu.org
Subject: Re: Patch for gdb build on hppa hp-ux
Date: Tue, 10 Apr 2007 20:22:00 -0000 [thread overview]
Message-ID: <20070410202213.GA778@caradoc.them.org> (raw)
In-Reply-To: <umz1gkq68.fsf@gnu.org>
On Tue, Apr 10, 2007 at 10:03:27PM +0300, Eli Zaretskii wrote:
> > + SOM-encapsulated symbolic debugging information, automatic
> > + invocation of pxdb, and the aCC custom C++ ABI.
>
> This is not a complete sentence.
This is a list of items and descriptions; the other items are:
target abug
target cpu32bug
target est
target rom68k
Various m68k-only ROM monitors.
DWARF 1 support
A debug information format. The predecessor to DWARF 2 and
DWARF 3, which are still supported.
Would you rather I used complete sentences throughout, or is that too
wordy?
I'm asking since I have a sizable patch deleting everything else
from the list of obsolete files, and that adds another dozen things to
this list.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-10 20:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 21:53 Steve Ellcey
2007-04-07 17:20 ` Daniel Jacobowitz
2007-04-09 2:13 ` Daniel Jacobowitz
2007-04-09 23:25 ` Steve Ellcey
2007-04-10 12:05 ` Daniel Jacobowitz
2007-04-10 12:11 ` Daniel Jacobowitz
2007-04-10 17:32 ` Steve Ellcey
2007-04-10 17:41 ` Daniel Jacobowitz
2007-04-10 19:03 ` Eli Zaretskii
2007-04-10 20:22 ` Daniel Jacobowitz [this message]
2007-04-13 14:04 ` Daniel Jacobowitz
2007-04-13 17:07 ` [patch] "single step" atomic instruction sequences as a whole on PPC Luis Machado
2007-04-28 23:34 ` [RFC] " Luis Machado
2007-04-28 23:45 ` Ulrich Weigand
2007-04-29 1:53 ` Luis Machado
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=20070410202213.GA778@caradoc.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=sje@cup.hp.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