From: Pedro Alves <palves@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: David Michael <fedora.dm0@gmail.com>,
bug-hurd@gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] GDB Hurd Fixes
Date: Mon, 06 Jan 2014 17:25:00 -0000 [thread overview]
Message-ID: <52CAE708.8050607@redhat.com> (raw)
In-Reply-To: <87vbxxhww4.fsf@kepler.schwinge.homeip.net>
On 01/06/2014 04:56 PM, Thomas Schwinge wrote:
> Hi!
>
> Sorry for the delay, and thanks for the patches you posted. Here are
> three patches, based on yours, that I intend to apply if there are no
> further comments.
I have no further comments (other than saying that IWBN to
have the rationale for the changes end up in the commit log).
Thanks,
--
Pedro Alves
next prev parent reply other threads:[~2014-01-06 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 0:43 David Michael
2013-09-20 8:47 ` Pedro Alves
2013-09-20 8:55 ` Thomas Schwinge
2013-09-20 15:17 ` David Michael
2014-01-06 16:56 ` Thomas Schwinge
2014-01-06 17:25 ` Pedro Alves [this message]
2014-05-06 3:49 ` Samuel Bronson
2014-05-06 6:42 ` Thomas Schwinge
2016-01-12 12:01 ` Hurd: Make gdb/reply_mig_hack.awk script compatible to "mawk" (was: [RFC] GDB Hurd Fixes) Thomas Schwinge
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=52CAE708.8050607@redhat.com \
--to=palves@redhat.com \
--cc=bug-hurd@gnu.org \
--cc=fedora.dm0@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=thomas@codesourcery.com \
/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