From: Ulrich Drepper <drepper@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: i386/strchr.S broken?
Date: Sat, 10 Aug 2002 11:01:00 -0000 [thread overview]
Message-ID: <3D5554DA.4090900@redhat.com> (raw)
In-Reply-To: <u8r8h6hcl1.fsf@gromit.moeb>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Jaeger wrote:
> Ignore the patch - I understand the algorithm now. But now I'd like
> to add a comment to it.
>
> Ok to commit to mainline?
Yes, go on.
- --
- ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9VVTe2ijCOnn/RHQRAlIKAJ9j7UGvRrTpCdjXZfVpRAmQYunJ/QCfdKt2
MHovDK9bwlREs2EUj+6r2ek=
=escG
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2002-08-10 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 9:54 Andreas Jaeger
2002-08-10 10:02 ` Andreas Jaeger
2002-08-10 11:01 ` 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=3D5554DA.4090900@redhat.com \
--to=drepper@redhat.com \
--cc=aj@suse.de \
--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).