Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb/dap: add option commandEscapePrefix
Date: Wed, 19 Nov 2025 11:52:09 -0700	[thread overview]
Message-ID: <875xb5rh2e.fsf@tromey.com> (raw)
In-Reply-To: <861plym33x.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 Nov 2025 17:03:30 +0200")

>> Sorry, I don't know.

Eli> It's a new feature, no?  If so, it warrants to be called out in NEWS.

FWIW I agree.  Oleg, the relevant section for gdb 17 looks like:

    * Debugger Adapter Protocol changes

      ** GDB now emits the "process" event.
    [...]

So you can just add a section like this in the "since gdb 17" section.
I'd probably stick it before the Python API section.  I don't think we
have a usual ordering.

thanks
Tom

  reply	other threads:[~2025-11-19 18:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 14:26 oltolm
2025-11-16 14:31 ` Eli Zaretskii
2025-11-16 14:33   ` Oleg Tolmatcev
2025-11-16 15:03     ` Eli Zaretskii
2025-11-19 18:52       ` Tom Tromey [this message]
2025-11-19 18:54 ` Tom Tromey

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=875xb5rh2e.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=oleg.tolmatcev@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