From: Roland McGrath <roland@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [RFC PATCH] Kill some duplication between 64-bit linux arches
Date: Tue, 23 Mar 2004 23:58:00 -0000 [thread overview]
Message-ID: <200403231943.i2NJhpuL005639@magilla.sf.frob.com> (raw)
In-Reply-To: Ulrich Drepper's message of Tuesday, 23 March 2004 11:37:57 -0800 <40609215.4070709@redhat.com>
> Let's move it all the sysdeps/unix/sysv/linux/wordsize-64. *Iff* tthere
> should ever be another need for this code it still can be moved.
Agreed. Just a note to future hackers, that moving this code rather than
duplicating it will be the right thing.
next prev parent reply other threads:[~2004-03-23 19:43 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 [this message]
2004-03-24 0:04 ` Jakub Jelinek
2004-03-24 12:00 ` Jakub Jelinek
2004-03-24 15:25 ` 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=200403231943.i2NJhpuL005639@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=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).