From: Tom Tromey <tom@tromey.com>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/reverse: update error message for "reverse-" commands
Date: Fri, 24 Oct 2025 12:42:12 -0600 [thread overview]
Message-ID: <87o6pwgn0b.fsf@tromey.com> (raw)
In-Reply-To: <20251023183342.219421-1-guinevere@redhat.com> (Guinevere Larsen's message of "Thu, 23 Oct 2025 15:33:42 -0300")
>>>>> "Guinevere" == Guinevere Larsen <guinevere@redhat.com> writes:
Guinevere> This commit changes the message to avoid the internal terminology, and
Guinevere> to add a hint that the user may need to create a recording somehow to be
Guinevere> able to execute in reverse.
FWIW it seems fine to me.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2025-10-24 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 18:33 Guinevere Larsen
2025-10-24 18:42 ` Tom Tromey [this message]
2025-10-24 18:44 ` Guinevere Larsen
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=87o6pwgn0b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@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