From: Tom Tromey <tom@tromey.com>
To: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: Re: [PATCH] Fix (most) OpenBSD link errors
Date: Wed, 04 Dec 2019 21:05:00 -0000 [thread overview]
Message-ID: <87r21jajio.fsf@tromey.com> (raw)
In-Reply-To: <20191122170716.223190-1-cbiesinger@google.com> (Christian Biesinger via gdb-patches's message of "Fri, 22 Nov 2019 11:07:16 -0600")
>>>>> "Christian" == Christian Biesinger via gdb-patches <gdb-patches@sourceware.org> writes:
I didn't see a reply to this one.
Christian> 2019-11-22 Christian Biesinger <cbiesinger@google.com>
Christian> * configure.nat (obsd64): Add missing files x86-nat.o and
Christian> nat/x86-dregs.o.
Looks good, thank you.
Tom
next prev parent reply other threads:[~2019-12-04 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 17:07 Christian Biesinger via gdb-patches
2019-12-04 21:05 ` Tom Tromey [this message]
2019-12-04 22:17 ` Christian Biesinger via gdb-patches
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=87r21jajio.fsf@tromey.com \
--to=tom@tromey.com \
--cc=cbiesinger@google.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