From: Tom Tromey <tom@tromey.com>
To: "Flávio Cruz" <flaviocruz@gmail.com>
Cc: Tom Tromey <tom@tromey.com>,
gdb-patches <gdb-patches@sourceware.org>,
Simon Marchi <simark@simark.ca>,
Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: [PATCH] Hurd: do not include defs.h when compiling MiG stubs since they are compiled as C files
Date: Tue, 17 Dec 2024 10:39:51 -0700 [thread overview]
Message-ID: <874j32cioo.fsf@tromey.com> (raw)
In-Reply-To: <CAKwpGPx1LKDuXmLyZ=QDQ_vzLFHLiqCaSJKaMdrpeVLrXv8R0w@mail.gmail.com> (=?utf-8?Q?=22Fl=C3=A1vio?= Cruz"'s message of "Tue, 17 Dec 2024 12:06:02 -0500")
Flávio> Yes, this is still relevant and can be applied cleanly.
Thank you. I'm pushing it now.
Tom
prev parent reply other threads:[~2024-12-17 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 22:05 Flavio Cruz
2024-12-17 16:45 ` Tom Tromey
2024-12-17 17:06 ` Flávio Cruz
2024-12-17 17:39 ` Tom Tromey [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=874j32cioo.fsf@tromey.com \
--to=tom@tromey.com \
--cc=flaviocruz@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=samuel.thibault@gnu.org \
--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