From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: Fwd: [RFA] mixed source+assembly from cli disassemble
Date: Tue, 29 Apr 2008 00:54:00 -0000 [thread overview]
Message-ID: <u3ap5zu0u.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0804280713q1d6419aasfccfaaee0e7d4710@mail.gmail.com>
> Date: Mon, 28 Apr 2008 07:13:05 -0700
> From: "Doug Evans" <dje@google.com>
> Cc: "Joel Brobecker" <brobecker@adacore.com>,
> "GDB Patches" <gdb-patches@sourceware.org>
>
> Ping. Eli, Joel requests review of the doc parts of this patch.
Yes, sorry I missed it.
> > > c = add_com ("disassemble", class_vars, disassemble_command, _("\
> > > Disassemble a specified section of memory.\n\
> > > Default is the function surrounding the pc of the selected frame.\n\
> > > +With a /m modifier source lines, if available, are included.\n\
> >
> > I'd like to have Eli's feedback on this change. I would phrase
> > differently (the current form is missing a coma to make it
> > intelligible):
> >
> > With a /m modifier, source lines are included (if available).
I like the latter wording better, too.
> @item disassemble
> +@itemx disassemble /@var{m}
It is wrong to use @var here, because "/m" is a literal string, it
doesn't stand for anything else.
Other than that, I'm okay with the doco changes. Thanks.
next prev parent reply other threads:[~2008-04-28 19:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 3:26 Doug Evans
2008-04-04 9:17 ` Michael Snyder
2008-04-04 9:26 ` Doug Evans
2008-04-04 9:58 ` Eli Zaretskii
2008-04-09 22:27 ` Michael Snyder
2008-04-10 12:35 ` Joel Brobecker
2008-04-11 8:55 ` Michael Snyder
2008-04-15 20:32 ` Michael Snyder
2008-04-16 21:16 ` Joel Brobecker
2008-04-16 21:22 ` Doug Evans
2008-04-16 22:49 ` Doug Evans
2008-04-17 21:29 ` Joel Brobecker
2008-04-17 22:01 ` Daniel Jacobowitz
2008-04-17 22:45 ` Joel Brobecker
2008-04-28 18:52 ` Fwd: " Doug Evans
2008-04-29 0:54 ` Eli Zaretskii [this message]
2008-05-06 3:15 ` Doug Evans
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=u3ap5zu0u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
/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