From: Ulrich Drepper <drepper@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>, libc-hacker@sources.redhat.com
Subject: Re: gscope + private_futex for alpha
Date: Fri, 25 May 2007 17:53:00 -0000 [thread overview]
Message-ID: <46572280.7090500@redhat.com> (raw)
In-Reply-To: <20070525161342.GA11528@twiddle.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Henderson wrote:
> Yeah, Jakub puts the flag in a ppc specific place. I thought it
> used the same scheme as ia64 and alpha though, and it would seem
> the common header would be ideal.
It's really a toss up. Jakub mentioned that he thought your approach is
good. We'll see whether it's better in his opinion to warrant him
writing another patch.
- --
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGVyKA2ijCOnn/RHQRAri8AJ9yyoFcDhQz62UXKQWPWhgiPrmXDACgmVwg
vkRl6gFBj8D1tlrf2TK2tyQ=
=/eVj
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-05-25 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 0:35 Richard Henderson
2007-05-25 2:26 ` Ulrich Drepper
2007-05-25 17:40 ` Richard Henderson
2007-05-25 17:53 ` Ulrich Drepper [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=46572280.7090500@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).