From: Tom Tromey <tom@tromey.com>
To: Gregory Anders via Gdb-patches <gdb-patches@sourceware.org>
Cc: Gregory Anders <greg@gpanders.com>
Subject: Re: [PATCH v2 0/4] DAP fixups
Date: Wed, 20 Sep 2023 11:40:19 -0600 [thread overview]
Message-ID: <87h6no7ngc.fsf@tromey.com> (raw)
In-Reply-To: <20230901210422.58003-1-greg@gpanders.com> (Gregory Anders via Gdb-patches's message of "Fri, 1 Sep 2023 16:02:16 -0500")
>>>>> "Gregory" == Gregory Anders via Gdb-patches <gdb-patches@sourceware.org> writes:
Gregory> v2 includes test cases for the breakpoint and source location changes as
Gregory> well as the change proposed by Tom Tromey to enforce **args parameter.
Gregory's copyright assignment came through. I've applied this series
locally and tested it; I am going to push it now.
Gregory, if you are planning to do more work on gdb, let me know
off-list and we can get you set up with write-after-approval access.
Thank you for the patches.
Tom
prev parent reply other threads:[~2023-09-20 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 21:02 Gregory Anders
2023-09-01 21:02 ` [PATCH v2 1/4] gdb/dap: check for breakpoint source before unpacking Gregory Anders
2023-09-01 21:02 ` [PATCH v2 2/4] gdb/dap: ignore unused keyword args in step_out Gregory Anders
2023-09-01 21:02 ` [PATCH v2 3/4] gdb/dap: use breakpoint fullname to resolve source Gregory Anders
2023-09-01 21:02 ` [PATCH v2 4/4] gdb/dap: only include sourceReference if file path does not exist Gregory Anders
2023-09-20 17:40 ` Tom Tromey [this message]
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=87h6no7ngc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=greg@gpanders.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).