This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Remove PRI_MACROS_BROKEN define usage
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Carlos O'Donell <carlos at redhat dot com>, Adhemerval Zanella <azanella at linux dot vnet dot ibm dot com>, <libc-alpha at sourceware dot org>
- Date: Fri, 2 May 2014 12:27:40 -0700 (PDT)
- Subject: Re: [PATCH] Remove PRI_MACROS_BROKEN define usage
- Authentication-results: sourceware.org; auth=none
- References: <532B3168 dot 2030108 at linux dot vnet dot ibm dot com> <Pine dot LNX dot 4 dot 64 dot 1403201832040 dot 29670 at digraph dot polyomino dot org dot uk> <532B3750 dot 2030102 at linux dot vnet dot ibm dot com> <Pine dot LNX dot 4 dot 64 dot 1403201848000 dot 29670 at digraph dot polyomino dot org dot uk> <532B3F64 dot 6030005 at linux dot vnet dot ibm dot com> <53634D52 dot 8010502 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1405021511400 dot 1748 at digraph dot polyomino dot org dot uk>
> I don't think gettext releases are relevant to us; it's the development
> sources of glibc's libintl that we should aim to have in sync with the
> development sources of gettext's libintl, by merging local changes in both
> directions and implementing things in such a way that identical code can
> work in both places.
Agreed. We don't worry about releasedness for any of the code we share
with other GNU projects. We vet the changes like any other changes and
rely on our own vetting and our own testing. Of course, for any shared
file whose source of truth changes more often than once in a blue moon,
it's wise to pay attention to the owning project and make sure we've kept
up with all its changes when either that project or libc is nearing release.