From: Eli Zaretskii <eliz@gnu.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org, achronop@gmail.com, blarsen@redhat.com
Subject: Re: [PATCH] Change message when reaching end of reverse history.
Date: Thu, 04 Apr 2024 10:00:58 +0300 [thread overview]
Message-ID: <8634s18vdh.fsf@gnu.org> (raw)
In-Reply-To: <DM8PR11MB5749EE909067C05A2945D444DE3C2@DM8PR11MB5749.namprd11.prod.outlook.com> (markus.t.metzger@intel.com)
> From: "Metzger, Markus T" <markus.t.metzger@intel.com>
> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, "Alex
> Chronopoulos" <achronop@gmail.com>, Guinevere Larsen <blarsen@redhat.com>
> Date: Thu, 4 Apr 2024 06:22:14 +0000
>
> I see no reason for changing the existing portion. The message is short enough:
>
> No more reverse-execution history. Recording will continue.
>
> Eli, are you OK with that change?
I don't think I ever chimed into this discussion, and I'm not sure I
even understand the issue well enough. But just on the face of it:
doesn't a bare "Recording will continue" fail to say anything about
the execution, which AFAIU also switches to some other mode in this
case?
If the above makes no sense, would someone please explain in more
detail what was the original issue, and I will try to come up with a
better suggestion.
next prev parent reply other threads:[~2024-04-04 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:48 Alex Chronopoulos
2024-03-14 6:37 ` Metzger, Markus T
2024-03-14 10:26 ` Guinevere Larsen
2024-03-14 17:26 ` Alex Chronopoulos
2024-04-03 17:54 ` Guinevere Larsen
2024-04-03 21:15 ` Alex Chronopoulos
2024-04-04 6:22 ` Metzger, Markus T
2024-04-04 7:00 ` Eli Zaretskii [this message]
2024-04-04 12:16 ` Guinevere Larsen
2024-04-04 12:39 ` Eli Zaretskii
2024-04-04 17:26 ` Guinevere Larsen
2024-04-04 19:55 ` Alex Chronopoulos
2024-04-05 5:18 ` Metzger, Markus T
2024-04-05 15:43 ` Guinevere Larsen
2024-03-14 14:53 ` Tom Tromey
2024-03-14 16:13 ` Metzger, Markus T
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=8634s18vdh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=achronop@gmail.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).