From: Jan Vrany <jan.vrany@labware.com>
To: Joel Brobecker <brobecker@adacore.com>,
Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCHv3] gdb/python/mi: create MI commands using python
Date: Sun, 13 Feb 2022 21:46:41 +0000 [thread overview]
Message-ID: <a7bfcf727f61cdf461070de49f5d37ff7b6f9c23.camel@labware.com> (raw)
In-Reply-To: <YgkVRx0n5/COxv70@adacore.com>
Hi Joel,
On Sun, 2022-02-13 at 18:27 +0400, Joel Brobecker wrote:
> Hi Andrew and Jan,
>
> I'm trying to keep track of this patch series in relation to the GDB 12
> release. This was requested by Andrew when I first suggested we start
> working on that release.
>
> Andrew send me the following link...
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceware.org_pipermail_gdb-2Dpatches_2022-2DJanuary_185332.html&d=DwIBAg&c=sPZ6DeHLiehUHQWKIrsNwWp3t7snrE-az24ztT0w7Jc&r=WpFFGgYa98Yp-c29WHTCwU1wAGFBvszA6a4RzgpMSqc&m=k-1bsYWC541K5oo2QXDgJKmS_rYbszy_0EulyjUipVk&s=MT3A9mLXoH0L507fRUP-VwrlZDmiVDnlG1NxnnMXO9o&e=
>
> ... which pointed to a 5-commits series, and now I see single-commit
> v2 and v3 patches. Can you summarize for me what happened to each of
> the 5 patches, and the status of each patch?
>
"My" 5-commit series is abandoned in favour of Andrew's 1-commit version
(the v2 and v3).
After I posted my (5-commit) version, Andrew came up with his (1-commit)
version based on mine. It's essentially my 5 commits squashed and
significantly modified to use different internal implementation and adding
some useful features. I believe we all agree to proceed with Andrew's as
it is arguably nicer. AFAIK all comments on my original series have been
addressed in Andrew's v2.
So, v3 is the latest iteration of this code and would be nice to have
in GDB 12 (once everyone's happy with it, indeed).
Thanks!
Jan
next prev parent reply other threads:[~2022-02-13 21:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 12:44 [PATCH 0/5] create GDB/MI " Jan Vrany
2022-01-17 12:44 ` [PATCH 1/5] gdb/mi: introduce new class mi_command_builtin Jan Vrany
2022-01-17 12:44 ` [PATCH 2/5] gdb/python: create GDB/MI commands using python Jan Vrany
2022-02-06 16:52 ` Lancelot SIX
2022-01-17 12:44 ` [PATCH 3/5] gdb/python: allow redefinition of python GDB/MI commands Jan Vrany
2022-02-06 17:13 ` Lancelot SIX
2022-02-06 20:33 ` Simon Marchi
2022-02-06 20:44 ` Jan Vrany
2022-02-06 20:46 ` Simon Marchi
2022-02-07 9:46 ` Lancelot SIX
2022-01-17 12:44 ` [PATCH 4/5] gdb/testsuite: add tests for python-defined MI commands Jan Vrany
2022-01-17 12:44 ` [PATCH 5/5] gdb/python: document GDB/MI commands in Python Jan Vrany
2022-01-17 13:15 ` Eli Zaretskii
2022-01-17 13:20 ` Eli Zaretskii
2022-01-18 12:34 ` Jan Vrany
2022-01-18 15:09 ` Eli Zaretskii
2022-01-18 13:55 ` [PATCH 0/5] create GDB/MI commands using python Andrew Burgess
2022-01-18 15:13 ` Jan Vrany
2022-01-21 15:22 ` Andrew Burgess
2022-01-24 12:59 ` Jan Vrany
2022-02-02 16:57 ` Andrew Burgess
2022-02-06 21:16 ` Simon Marchi
2022-02-07 15:56 ` [PATCHv2] gdb/python/mi: create MI " Andrew Burgess
2022-02-08 15:16 ` Simon Marchi
2022-02-09 12:25 ` [PATCHv3] " Andrew Burgess
2022-02-09 14:08 ` Simon Marchi
2022-02-10 18:26 ` Andrew Burgess
2022-02-13 14:27 ` Joel Brobecker
2022-02-13 21:46 ` Jan Vrany [this message]
2022-02-24 10:37 ` [PATCHv4] " Andrew Burgess
2022-02-25 19:22 ` Tom Tromey
2022-02-25 19:31 ` Jan Vrany
2022-02-28 16:48 ` [PATCHv5] " Andrew Burgess
2022-02-28 18:40 ` Tom Tromey
2022-03-13 4:47 ` Joel Brobecker
2022-03-14 14:13 ` Andrew Burgess
2022-03-16 8:10 ` Joel Brobecker
2022-03-16 12:29 ` Simon Marchi
2022-03-18 15:06 ` Simon Marchi
2022-03-18 16:12 ` Andrew Burgess
2022-03-18 19:57 ` Simon Marchi
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=a7bfcf727f61cdf461070de49f5d37ff7b6f9c23.camel@labware.com \
--to=jan.vrany@labware.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).