From: Matheus Branco Borella <dark.ryu.550@gmail.com>
To: gdb-patches@sourceware.org
Cc: eli@gnu.org
Subject:
Date: Tue, 16 Jan 2024 14:50:30 -0300 [thread overview]
Message-ID: <20240116175030.9456-1-dark.ryu.550@gmail.com> (raw)
In-Reply-To: <83edehcuqu.fsf@gnu.org>
next prev parent reply other threads:[~2024-01-16 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 4:54 [PATCH v4] Add support for creating new types from the Python API Matheus Branco Borella
2024-01-16 12:45 ` Eli Zaretskii
2024-01-16 17:50 ` Matheus Branco Borella [this message]
2024-01-16 18:20 ` Matheus Branco Borella
2024-01-16 18:56 ` Eli Zaretskii
2024-01-16 21:27 ` Matheus Branco Borella
2024-02-06 18:20 ` Tom Tromey
2024-02-21 18:11 ` Matheus Branco Borella
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=20240116175030.9456-1-dark.ryu.550@gmail.com \
--to=dark.ryu.550@gmail.com \
--cc=eli@gnu.org \
--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).