Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jeremy Bryant <jb@jeremybryant.net>
Cc: gdb-patches@sourceware.org, simon.marchi@polymtl.ca, simark@simark.ca
Subject: Re: [PATCH] - Adapt to Python-3 print syntax
Date: Wed, 15 Oct 2025 15:01:29 +0300	[thread overview]
Message-ID: <86cy6oe5ly.fsf@gnu.org> (raw)
In-Reply-To: <87frbl8724.fsf@jeremybryant.net> (message from Jeremy Bryant on Tue, 14 Oct 2025 23:14:27 +0100)

> From: Jeremy Bryant <jb@jeremybryant.net>
> Cc: Simon Marchi <simon.marchi@polymtl.ca>, Simon Marchi <simark@simark.ca>,
>  Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 14 Oct 2025 23:14:27 +0100
> 
> This change adapts doc examples to Python 3 so they work on current
> installations.
> 
> python.texi uses a mixture of Python 3 and Python 2 print syntax, the
> latter having been sunsetted several years ago.
> 
> Adding Eli as "Responsible Maintainer" for documentation.
> Also adding Simon Marchi who from recent commits may have an interest in this
> part of GDB and may have comments or suggestions.
> 
> Perhaps this patch falls under "The Obvious Fix Rule".
> The patch is provided inline for critique and also as attachment.
> If I have missed any conventions please state so.

Thanks for CC'ing me, but this is not a documentation issue.  This is
about what syntax to show and document, so it's something that the
other maintainers need to decide.

  reply	other threads:[~2025-10-15 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 22:14 Jeremy Bryant
2025-10-15 12:01 ` Eli Zaretskii [this message]
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
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=86cy6oe5ly.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 \
    /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