From: Thomas Schwinge <thomas@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, libc-alpha@sourceware.org,
drepper@gmail.com, Carlos O'Donell <carlos@systemhalted.org>
Subject: Re: struct siginfo vs. siginfo_t
Date: Wed, 21 Mar 2012 13:45:00 -0000 [thread overview]
Message-ID: <87iphyf4p6.fsf@schwinge.name> (raw)
In-Reply-To: <4F69C79C.7090606@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
Hi!
Pedro Alves, true master of GNU ChangeLog syntax as well as quick patch
review. Thanks!
Thusly changed and committed. (And I have no idea how that pasto
happened.)
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2012-03-21 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120226181752.1175.qmail@sourceware.org>
[not found] ` <87zkbhkipp.fsf@schwinge.name>
[not found] ` <CADZpyiwXDJSPRDoQpA3ZOTYsznMc_2DrVpr3z0y-zt2z5FjkRQ@mail.gmail.com>
2012-03-21 11:51 ` Thomas Schwinge
2012-03-21 12:21 ` Pedro Alves
2012-03-21 13:45 ` Thomas Schwinge [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=87iphyf4p6.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=carlos@systemhalted.org \
--cc=drepper@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=libc-alpha@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