public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [RFC PATCH] Kill some duplication between 64-bit linux arches
Date: Wed, 24 Mar 2004 15:25:00 -0000	[thread overview]
Message-ID: <4060D08D.50008@redhat.com> (raw)
In-Reply-To: <20040323214903.GH15946@sunsite.ms.mff.cuni.cz>

Jakub Jelinek wrote:

> FYI the patch passed make check on ia64, ppc64, x86-64 and so far looks good
> on s390x as well (passed linuxthreads make check, NPTL make check still
> running).

Passes my tests, too.  I've applied it.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖

      reply	other threads:[~2004-03-24  0:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 19:32 Jakub Jelinek
2004-03-23 19:38 ` Ulrich Drepper
2004-03-23 19:43   ` Roland McGrath
2004-03-23 20:37     ` Ulrich Drepper
2004-03-23 23:58       ` Roland McGrath
2004-03-24  0:04   ` Jakub Jelinek
2004-03-24 12:00     ` Jakub Jelinek
2004-03-24 15:25       ` 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=4060D08D.50008@redhat.com \
    --to=drepper@redhat.com \
    --cc=jakub@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).