From: Eli Zaretskii <eliz@gnu.org>
To: teawater <teawater@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Process record and replay, 10/10
Date: Sat, 08 Nov 2008 09:25:00 -0000 [thread overview]
Message-ID: <ubpwqsh9r.fsf@gnu.org> (raw)
In-Reply-To: <daef60380811072039q14573f03kff6525121a0d5b19@mail.gmail.com>
> Date: Sat, 8 Nov 2008 12:39:44 +0800
> From: teawater <teawater@gmail.com>
> Cc: gdb-patches@sourceware.org
>
> >> +@chapter Recording programs running message and replay it
> >
> > I don't understand this phrase. What did you want to say? what does
> > the word "message" have to do with this feature?
>
> What about "Recording inferior execute log and replay it"?
If this is the intent, then I suggest simply
Recording inferior's execution and replaying it
(The fact that you record execution log is an implementation detail,
and certainly does not need to be stated in the chapter's name.)
> > Is the command "target record" or just "record"? or is the latter an
> > alias of the former? We need to explain all this in the manual,
> > because the @item says "target record", while in the last sentence
> > above you say that the command is "record"
>
> "target record" is the real command.
> "record" is a command call "target record". I want it to be the alias
> of "target record"
> "rec" is a alias of "record".
The aliases should be described in the manual.
> What about change "@code{record}" to "@code{target record}"?
Fine with me.
> > By the way, I think we need a NEWS entry for this feature.
> >
>
> What about add this:
>
> * Process record and replay
>
> Record inferior execute log and replay it.
OK, but I think at least one or two more sentences describing the
feature would be nice.
next prev parent reply other threads:[~2008-11-08 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 7:53 teawater
2008-11-07 14:49 ` Eli Zaretskii
2008-11-08 4:40 ` teawater
2008-11-08 9:25 ` Eli Zaretskii [this message]
2008-11-11 5:43 ` teawater
2008-11-14 16:04 ` Eli Zaretskii
2008-11-14 16:29 ` teawater
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=ubpwqsh9r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--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