From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: tom@tromey.com, gdb-patches@sourceware.org,
simon.marchi@polymtl.ca, simark@simark.ca
Subject: Re: Ready for Write After Approval - Re: [PATCH v2] - Adapt to Python-3 print syntax
Date: Fri, 17 Oct 2025 14:25:42 +0300 [thread overview]
Message-ID: <861pn1hirt.fsf@gnu.org> (raw)
In-Reply-To: <87frbik3zr.fsf@jeremybryant.net> (message from Jeremy Bryant on Thu, 16 Oct 2025 21:04:24 +0100)
> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: GDB Patches <gdb-patches@sourceware.org>, Simon Marchi
> <simon.marchi@polymtl.ca>, Simon Marchi <simark@simark.ca>, Eli
> Zaretskii <eliz@gnu.org>
> Date: Thu, 16 Oct 2025 21:04:24 +0100
>
> Tom Tromey <tom@tromey.com> writes:
>
> > Jeremy> Thanks Tom, I've corrected the discrepancy and now all changes are
> > Jeremy> consistent. See revised patch v2 inline below for critique and attached
> > Jeremy> for completeness.
> > Jeremy> In the course of this, I've also removed a pre-existing extraneous space.
> >
> > Jeremy> WDYT?
> >
> > Looks good, thank you.
> > Approved-By: Tom Tromey <tom@tromey.com>
> >
> > Tom
>
> Thanks Tom.
>
> I see the patch is not yet committed.
>
> Would someone on the "Write After Approval" list please commit the
> patch?
I think you expect too much from the GDB maintenance processes. One
day is nowhere near enough to ping about approved-but-not-committed
changes.
next prev parent reply other threads:[~2025-10-17 11:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 22:14 [PATCH] " Jeremy Bryant
2025-10-15 12:01 ` Eli Zaretskii
2025-10-15 13:44 ` Tom Tromey
2025-10-15 20:19 ` [PATCH v2] " Jeremy Bryant
2025-10-15 20:32 ` Tom Tromey
2025-10-16 20:04 ` Ready for Write After Approval - " Jeremy Bryant
2025-10-17 11:25 ` Eli Zaretskii [this message]
2025-10-19 19:16 ` Contributor guidelines - " Jeremy Bryant
2025-10-20 2:25 ` Eli Zaretskii
2025-10-17 14:45 ` Tom Tromey
2025-10-19 17:02 ` Thank you - " Jeremy Bryant
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=861pn1hirt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jb@jeremybryant.net \
--cc=simark@simark.ca \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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