public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Alex Chronopoulos <achronop@gmail.com>,
	 "Eli Zaretskii (eliz@gnu.org)" <eliz@gnu.org>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Change message when reaching end of reverse history.
Date: Thu, 14 Mar 2024 08:53:15 -0600	[thread overview]
Message-ID: <87frwslvac.fsf@tromey.com> (raw)
In-Reply-To: <DM8PR11MB574989297348040011085CC5DE292@DM8PR11MB5749.namprd11.prod.outlook.com> (Markus T. Metzger's message of "Thu, 14 Mar 2024 06:37:57 +0000")

>>>>> Metzger, Markus T <markus.t.metzger@intel.com> writes:

> We should probably give MI a similar indication, although that would likely
> break existing MI consumers.  Not sure how opt-in is handled in MI.

I thought perhaps this change was just about being more clear to users
-- which isn't really a concern for MI consumers.  So my first reaction
is to wonder if this really is needed for MI.

Anyway in MI there are a few ways to change things without breaking
consumers.  One way is to add a new field to the output.  Another way is
opt-in behavior -- a new command to enable the new behavior, or simply
enabling it in the "next" MI version.

Tom

  parent reply	other threads:[~2024-03-14 14:53 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
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 [this message]
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=87frwslvac.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=achronop@gmail.com \
    --cc=eliz@gnu.org \
    --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).