From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: eggert@cs.ucla.edu, gdb-patches@sourceware.org
Subject: Re: reverse execution part of the manual is written backwards
Date: Thu, 11 Apr 2019 16:27:00 -0000 [thread overview]
Message-ID: <83r2a84iee.fsf@gnu.org> (raw)
In-Reply-To: <111cf816-c27c-fe5d-7cb8-31375ad1cbc2@redhat.com> (message from Pedro Alves on Thu, 11 Apr 2019 16:54:22 +0100)
> Cc: eggert@cs.ucla.edu, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 11 Apr 2019 16:54:22 +0100
>
> > In any case, I think the Reverse Execution section should say
> > something about the conditions for using this mode, regardless of
> > whether it precedes or follows the chapter about recording and
> > replaying. It probably should simply say what the above URL says at
> > its beginning, and then describe the commands to activate the correct
> > target, or point to a clear description of those commands elsewhere in
> > the manual. Because right now we have a description of record and
> > replay, and we have a description of reverse-execution commands, but
> > no "glue" to connect them, and there's no reasonable way for a reader
> > to guess what to do to bridge over that chasm.
> >
> > Do you agree?
> >
>
> How about this?
LGTM, thanks. Paul, does this address your concerns?
next prev parent reply other threads:[~2019-04-11 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 4:19 Paul Eggert
2019-04-10 11:51 ` Pedro Alves
2019-04-10 14:54 ` Eli Zaretskii
2019-04-11 15:55 ` Pedro Alves
2019-04-11 16:27 ` Eli Zaretskii [this message]
2019-04-22 6:50 ` Paul Eggert
2019-04-22 11:50 ` Pedro Alves
2019-04-10 15:13 ` Paul Eggert
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=83r2a84iee.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gdb-patches@sourceware.org \
--cc=palves@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