From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH 0/2] Rewrite make-target-delegates in Python
Date: Wed, 02 Mar 2022 09:10:45 -0700 [thread overview]
Message-ID: <87bkyojpx6.fsf@tromey.com> (raw)
In-Reply-To: <20220214192852.3637933-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Mon, 14 Feb 2022 12:28:50 -0700")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> This series rewrites make-target-delegates in Python. Perl is on the
Tom> wane a bit and I feel that, as a group, gdb has a bit more Python
Tom> expertise. Also, this lets us share the copyright-generation code,
Tom> which is reused both in this series, and in an upcoming series I'll be
Tom> sending in the future.
Tom> Tested by rebuilding, and by examining the diffs of the generated
Tom> files, which are minimal.
I'm checking this in.
Tom
prev parent reply other threads:[~2022-03-02 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 19:28 Tom Tromey
2022-02-14 19:28 ` [PATCH 1/2] Move copyright code from gdbarch.py to new file Tom Tromey
2022-02-14 19:28 ` [PATCH 2/2] Rewrite make-target-delegates in Python Tom Tromey
2022-03-02 16:19 ` Pedro Alves
2022-03-02 16:10 ` 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=87bkyojpx6.fsf@tromey.com \
--to=tromey@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).