From: Andreas Schwab <schwab@redhat.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Move __fortify_fail call out of line in x86 ____longjmp_chk
Date: Fri, 08 Apr 2011 12:57:00 -0000 [thread overview]
Message-ID: <m34o68c34l.fsf@redhat.com> (raw)
In-Reply-To: <BANLkTi=MrVdVLakdSV1Yc8O80-xcVTPTTw@mail.gmail.com> (Ulrich Drepper's message of "Fri, 8 Apr 2011 08:48:13 -0400")
That's how it should have been in the first place.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next prev parent reply other threads:[~2011-04-08 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 12:25 Andreas Schwab
2011-04-08 12:48 ` Ulrich Drepper
2011-04-08 12:57 ` Andreas Schwab [this message]
2011-04-08 13:04 ` Ulrich Drepper
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=m34o68c34l.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=drepper@gmail.com \
--cc=libc-hacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).