From: Thomas Schwinge <thomas@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, David Michael <fedora.dm0@gmail.com>
Cc: <bug-hurd@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [RFC] GDB Hurd Fixes
Date: Fri, 20 Sep 2013 08:55:00 -0000 [thread overview]
Message-ID: <87bo3n98jo.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <523C0B99.7080109@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
Hi!
On Fri, 20 Sep 2013 09:47:21 +0100, Pedro Alves <palves@redhat.com> wrote:
> On 09/20/2013 01:43 AM, David Michael wrote:
> > [Hurd/GDB issue]
>
> But, we're missing all the context on the gdb-patches@ side.
I'll have a look.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2013-09-20 8:55 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 [this message]
2013-09-20 15:17 ` David Michael
2014-01-06 16:56 ` Thomas Schwinge
2014-01-06 17:25 ` Pedro Alves
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=87bo3n98jo.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=bug-hurd@gnu.org \
--cc=fedora.dm0@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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