From: Eli Zaretskii <eliz@gnu.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org, pedro@palves.net, simark@simark.ca
Subject: Re: [PATCH] set/show python dont-write-bytecode fixes
Date: Sun, 24 Jul 2022 08:41:18 +0300 [thread overview]
Message-ID: <83h737gj9d.fsf@gnu.org> (raw)
In-Reply-To: <20220723143025.6fe4b0cd@f35-zws-1> (message from Kevin Buettner on Sat, 23 Jul 2022 14:30:25 -0700)
> Date: Sat, 23 Jul 2022 14:30:25 -0700
> From: Kevin Buettner <kevinb@redhat.com>
> Cc: gdb-patches@sourceware.org, pedro@palves.net, simark@simark.ca
>
> I've made some changes to the GDB manual too.
>
> These changes, including the ones you asked for in your earlier email,
> are in the v2 patch. See:
>
> https://sourceware.org/pipermail/gdb-patches/2022-July/191030.html
Thanks, I approved them.
prev parent reply other threads:[~2022-07-24 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 19:14 Kevin Buettner
2022-07-21 17:55 ` Pedro Alves
2022-07-21 23:08 ` Kevin Buettner
2022-07-22 6:40 ` Eli Zaretskii
2022-07-23 1:37 ` Kevin Buettner
2022-07-23 6:54 ` Eli Zaretskii
2022-07-23 21:30 ` Kevin Buettner
2022-07-24 5:41 ` Eli Zaretskii [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=83h737gj9d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=pedro@palves.net \
--cc=simark@simark.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).