From: Ulrich Drepper <drepper@redhat.com>
To: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] glibc build fixes
Date: Fri, 17 Feb 2006 15:37:00 -0000 [thread overview]
Message-ID: <43F5EDB6.9040909@redhat.com> (raw)
In-Reply-To: <20060217.222747.34764802.kkojima@rr.iij4u.or.jp>
[-- Attachment #1: Type: text/plain, Size: 109 bytes --]
Thanks, applied.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-02-17 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 13:02 Jakub Jelinek
2006-02-15 17:20 ` Ulrich Drepper
2006-02-17 13:27 ` Kaz Kojima
2006-02-17 15:37 ` Ulrich Drepper [this message]
2006-02-17 16:08 ` Jakub Jelinek
2006-02-17 18:23 ` Jakub Jelinek
2006-02-17 18:51 ` 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=43F5EDB6.9040909@redhat.com \
--to=drepper@redhat.com \
--cc=kkojima@rr.iij4u.or.jp \
--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).