From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add to documentation of Python 'dont_repeat' method
Date: Wed, 18 May 2022 12:53:01 -0600 [thread overview]
Message-ID: <87pmkad65u.fsf@tromey.com> (raw)
In-Reply-To: <20220219164753.3992479-1-tom@tromey.com> (Tom Tromey's message of "Sat, 19 Feb 2022 09:47:53 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> PR python/28533 points out that the Python 'dont_repeat' documentation
Tom> is a bit ambiguous about when the method ought to be called. This
Tom> patch spells it out.
Ping.
Tom
next prev parent reply other threads:[~2022-05-18 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 16:47 Tom Tromey
2022-05-18 18:53 ` Tom Tromey [this message]
2022-06-15 15:45 ` Tom Tromey
2022-06-15 17:35 ` Christian Biesinger
2022-06-15 18:03 ` Eli Zaretskii
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=87pmkad65u.fsf@tromey.com \
--to=tom@tromey.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).