From: Thomas Schwinge <tschwinge@gnu.org>
To: ams@gnu.org
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: Re: [gnu-nat] PATCH (part of PR #2534)
Date: Thu, 09 Oct 2008 16:09:00 -0000 [thread overview]
Message-ID: <20081009160610.GC19704@fencepost.gnu.org> (raw)
In-Reply-To: <20081007231026.GG7127@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 238 bytes --]
Hello!
On Wed, Oct 08, 2008 at 01:10:26AM +0200, I wrote:
> 2008-10-06 Thomas Schwinge <tschwinge@gnu.org>
>
> * Makefile.in: Revert 2008-09-10 change, as the problem is fixed
> upstream.
Committed.
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2008-10-09 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 17:38 [gnu-nat] PATCH (part of PR #2534) s/current_inferior/gnu_current_inf/g Pedro Alves
2008-10-07 18:03 ` Alfred M. Szmidt
2008-10-07 18:51 ` Pedro Alves
2008-10-07 18:58 ` Alfred M. Szmidt
2008-10-07 23:11 ` [gnu-nat] PATCH (part of PR #2534) Thomas Schwinge
2008-10-09 16:08 ` Thomas Schwinge
2008-10-07 23:13 ` Thomas Schwinge
2008-10-09 16:09 ` Thomas Schwinge [this message]
2008-10-10 11:41 ` Alfred M. Szmidt
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=20081009160610.GC19704@fencepost.gnu.org \
--to=tschwinge@gnu.org \
--cc=ams@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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