From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"pedro@codesourcery.com" <pedro@codesourcery.com>,
"teawater@gmail.com" <teawater@gmail.com>
Subject: Re: [RFA] doc for "info record"
Date: Thu, 22 Oct 2009 19:40:00 -0000 [thread overview]
Message-ID: <4AE0B37D.5000008@vmware.com> (raw)
In-Reply-To: <83d44ghb5n.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Wed, 21 Oct 2009 08:27:02 -0700
>> From: Michael Snyder <msnyder@vmware.com>
>>
>> Look ok to you Eli?
>
> Yes, with a few comments:
>
>> +Show various statistics about the state of process record and its
>> +in-memory execution log buffer, including:
>> +
>> +@table @code
>
> @table, and @code on top of that, is inappropriate for what you want
> here: a list of p[lain-text items. Please use @itemize @bullet or
> @itemize @minus. Note that with @itemize, you need to have each @item
> alone on its line, and the text should be on the following line, like
> this:
>
> @item
> Whether in record mode or replay mode.
>
>> +@item whether in record mode or replay mode.
>> +@item Lowest recorded instruction number (counting from when the current execution log started recording instructions).
>
> Please capitalize the first word of each @item consistently.
>
>> +@item Max number of instructions that may be contained in the execution log.
> ^^^
> No need to use abbreviations in a manual.
>
> Okay with these corrections.
Done, and committed.
next prev parent reply other threads:[~2009-10-22 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:33 Michael Snyder
2009-10-21 18:11 ` Eli Zaretskii
2009-10-22 19:40 ` Michael Snyder [this message]
2009-10-23 1:49 ` Hui Zhu
2009-10-22 12:57 ` Pedro Alves
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=4AE0B37D.5000008@vmware.com \
--to=msnyder@vmware.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=teawater@gmail.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