From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix ether_line
Date: Fri, 24 May 2002 01:28:00 -0000 [thread overview]
Message-ID: <1022228908.30693.298.camel@myware.mynet> (raw)
In-Reply-To: <20020523185956.M20867@sunsite.ms.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
On Thu, 2002-05-23 at 09:59, Jakub Jelinek wrote:
> ether_line ("0:c0:f0:46:5f:97 host.ether.com \t# comment", ...)
> would return 0:0:0:6:f:7 with -fwriteable-strings or segfault
> otherwise. The following patch fixes both bugs.
Right. Seems to be a very popular function. It's been around forever.
I've applied the patch. Thanks,
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-05-24 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 10:00 Jakub Jelinek
2002-05-24 1:28 ` 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=1022228908.30693.298.camel@myware.mynet \
--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).