This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug stdio/6530] *printf() and incomplete multibyte sequences returns -1 bogusly
- From: "joseph at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Sun, 24 Jun 2012 15:03:10 +0000
- Subject: [Bug stdio/6530] *printf() and incomplete multibyte sequences returns -1 bogusly
- Auto-submitted: auto-generated
- References: <bug-6530-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=6530
--- Comment #24 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-06-24 15:03:10 UTC ---
On Fri, 22 Jun 2012, carlos_odonell at mentor dot com wrote:
> > Based on experience from the sinking feeling of watching target milestones
> > slowly march forward on the Mozilla and Chromium bugtrackers: could you target
> > it at no particular milestone instead? That way, anyone stumbling on this will
> > realize that it is their own responsibility to get it fixed quickly if they
> > care for that to happen.
> >
> > Thanks,
> > Jonathan
>
> Jonathan, That's a discussion that should be had on libc-alpha@sourceware.org.
> Please start a thread there :-)
Yes, we do need to discuss how best to use milestones based on our
experiences of the 2.16 release cycle. Experience with bug trackers of
other problems would certainly be a useful contribution to that discussion
(and the related one of how to get bugs fixed faster than they are filed).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.