From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 2/3] scripts: Enhance glibcpp to do basic macro processing
Date: Tue, 13 Sep 2022 10:14:04 +0200 [thread overview]
Message-ID: <87edwfwv1v.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <b7e9cf60-5fe6-a96f-d4e4-5844223c54e6@gotplt.org> (Siddhesh Poyarekar's message of "Mon, 12 Sep 2022 16:49:59 -0400")
* Siddhesh Poyarekar:
> On 2022-09-05 09:44, Florian Weimer via Libc-alpha wrote:
>> ---
>> scripts/glibcpp.py | 317 +++++++++++++++++++++++++++++++++++++++++
>> support/Makefile | 10 +-
>> support/tst-glibcpp.py | 217 ++++++++++++++++++++++++++++
>> 3 files changed, 542 insertions(+), 2 deletions(-)
>> create mode 100644 support/tst-glibcpp.py
>
> OK except for a minor nit at the end; Copyright year for the new test
> file should be just 2022.
Fair enough, I've fixed it locally.
Thanks,
Florian
next prev parent reply other threads:[~2022-09-13 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 13:44 [PATCH 0/3] Parse <elf.h> in the glibcelf Python module Florian Weimer
2022-09-05 13:44 ` [PATCH 1/3] scripts: Extract glibcpp.py from check-obsolete-constructs.py Florian Weimer
2022-09-12 20:12 ` Siddhesh Poyarekar
2022-09-05 13:44 ` [PATCH 2/3] scripts: Enhance glibcpp to do basic macro processing Florian Weimer
2022-09-12 20:49 ` Siddhesh Poyarekar
2022-09-13 8:14 ` Florian Weimer [this message]
2022-09-05 13:44 ` [PATCH 3/3] elf: Extract glibcelf constants from <elf.h> Florian Weimer
2022-09-05 14:37 ` Florian Weimer
2022-09-13 17:34 ` Siddhesh Poyarekar
2022-09-14 10:06 ` Florian Weimer
2022-09-05 14:36 ` [PATCH 0/3] Parse <elf.h> in the glibcelf Python module Florian Weimer
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=87edwfwv1v.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).