From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix __register_printf_function
Date: Sat, 05 Apr 2003 00:34:00 -0000 [thread overview]
Message-ID: <200304050034.h350YHh05733@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Saturday, 5 April 2003 02:09:27 +0200 <20030405000927.GT16629@sunsite.ms.mff.cuni.cz>
> 2003-04-05 Jakub Jelinek <jakub@redhat.com>
>
> * stdio-common/reg-printf.c (__register_printf_function): Calloc
> instead of malloc __printf_arginfo_table and __printf_function_table.
> Reported by John Reiser <jreiser@BitWagon.com>.
I put this in.
Thanks,
Roland
prev parent reply other threads:[~2003-04-05 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 0:09 Jakub Jelinek
2003-04-05 0:34 ` Roland McGrath [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=200304050034.h350YHh05733@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).