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: "carlos_odonell at mentor dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 03 Oct 2012 00:54:00 +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 #31 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-10-03 00:54:00 UTC ---
(In reply to comment #30)
> Sure, no problem.
>
> Do I understand correctly that this means testing the patch against
> 2.16, 2.15, 2.14, 2.12, and 2.11 and then filing one bug for each
> branch describing the result?
Yes, that way we can track the backport to each branch individually and the
various release branch maintainers and the release branch shareholders can
comment on the change. The keyword allows a release branch manager to quickly
identify issues open against their branch.
If you have any feedback about this process I'd be more than happy to hear it.
We don't have much good formal process for bugzilla, but we're trying :-)
--
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.