public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsa at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/6846] Full featured printf hooks
Date: Fri, 06 Mar 2009 21:32:00 -0000	[thread overview]
Message-ID: <20090306213240.31677.qmail@sourceware.org> (raw)
In-Reply-To: <20080815064110.6846.rsa@us.ibm.com>


------- Additional Comments From rsa at us dot ibm dot com  2009-03-06 21:32 -------
Created an attachment (id=3796)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3796&action=view)
printf-hooks-2009-03-06.patch

I believe this satisfies all of Ulrich's requirements.	It fixes the remaining
issues from the previous patch:

3 separate format specifier arrays
user flags field in the printf_info struct
Single API for registration
No free function necessary (auto allocation)

Please review

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
Attachment #3787 is|0                           |1
           obsolete|                            |


http://sourceware.org/bugzilla/show_bug.cgi?id=6846

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2009-03-06 21:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15  6:42 [Bug libc/6846] New: " rsa at us dot ibm dot com
2008-08-15  6:44 ` [Bug libc/6846] " rsa at us dot ibm dot com
2008-08-15 23:29 ` rsa at us dot ibm dot com
2008-08-22 21:14 ` rsa at us dot ibm dot com
2008-08-22 21:38 ` rsa at us dot ibm dot com
2008-08-22 21:39 ` rsa at us dot ibm dot com
2008-08-22 21:40 ` rsa at us dot ibm dot com
2008-08-22 21:42 ` rsa at us dot ibm dot com
2008-08-22 21:43 ` rsa at us dot ibm dot com
2008-08-23 13:37 ` hjl dot tools at gmail dot com
2008-10-21 18:33 ` rsa at us dot ibm dot com
2008-11-25  7:41 ` drepper at redhat dot com
2008-11-25 17:47 ` rsa at us dot ibm dot com
2008-11-25 17:48 ` rsa at us dot ibm dot com
2008-11-25 19:13 ` rsa at us dot ibm dot com
2008-11-25 22:32 ` rsa at us dot ibm dot com
2009-02-27 23:08 ` rsa at us dot ibm dot com
2009-03-03  5:15 ` rsa at us dot ibm dot com
2009-03-03  5:26 ` rsa at us dot ibm dot com
2009-03-03  5:27 ` rsa at us dot ibm dot com
2009-03-06 21:32 ` rsa at us dot ibm dot com [this message]
2009-04-10  3:25 ` drepper at redhat dot com
2009-04-11  5:39 ` drepper at redhat dot com
2009-04-11  5:39 ` drepper at redhat dot com
2009-04-16 20:48 ` rsa at us dot ibm dot com
2009-04-16 21:30 ` rsa at us dot ibm dot com
2009-04-16 22:03 ` rsa at us dot ibm dot com
2009-04-16 22:41 ` drepper at redhat dot com
2009-04-17  1:38 ` rsa at us dot ibm dot com
2009-04-17  1:49 ` rsa at us dot ibm dot com
2009-04-17  2:22 ` rsa at us dot ibm dot com

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=20090306213240.31677.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).