From: Andrew Burgess <aburgess@redhat.com>
To: Matheus Branco Borella via Gdb-patches
<gdb-patches@sourceware.org>,
aburgess@readhat.com
Cc: dark.ryu.550@gmail.com, gdb-patches@sourceware.org
Subject: Re: [PATCHv3 0/2] Add __repr__() implementation to a few Python types
Date: Thu, 08 Jun 2023 19:46:04 +0100 [thread overview]
Message-ID: <87y1ktyeqb.fsf@redhat.com> (raw)
In-Reply-To: <20230607170556.1028183-1-dark.ryu.550@gmail.com>
Matheus Branco Borella via Gdb-patches <gdb-patches@sourceware.org>
writes:
> All of the changes look good in my oppinion. I'm still getting used to the hang
> of things, so I really appreciate the effort you put into making my patch more
> presentable! So I think it should be good to go?
I'll update, retest, and push these patches tomorrow.
Thanks,
Andrew
next prev parent reply other threads:[~2023-06-08 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3Cc9d2dc49-45c7-d6b9-c567-4ec78dd870a0>
2023-01-11 0:35 ` [PATCH] " Matheus Branco Borella
2023-01-18 17:05 ` Bruno Larsen
2023-01-18 18:02 ` Andrew Burgess
2023-01-19 8:23 ` Bruno Larsen
2023-01-20 1:43 ` Matheus Branco Borella
2023-01-20 16:45 ` Andrew Burgess
2023-01-24 14:45 ` Andrew Burgess
2023-05-18 3:33 ` Matheus Branco Borella
2023-05-19 21:27 ` [PATCHv3 0/2] " Andrew Burgess
2023-05-19 21:27 ` [PATCHv3 1/2] gdb: have mdict_size always return a symbol count Andrew Burgess
2023-05-19 21:27 ` [PATCHv3 2/2] gdb: add __repr__() implementation to a few Python types Andrew Burgess
2023-06-07 17:05 ` [PATCHv3 0/2] Add " Matheus Branco Borella
2023-06-08 18:46 ` Andrew Burgess [this message]
2023-06-09 12:33 ` Andrew Burgess
2023-07-04 11:09 ` Andrew Burgess
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=87y1ktyeqb.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=aburgess@readhat.com \
--cc=dark.ryu.550@gmail.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).