This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Release branch maintenance - Was: glibc 2.19 status?
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Allan McRae <allan at archlinux dot org>
- Cc: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, Siddhesh Poyarekar <siddhesh at redhat dot com>, Alexandre Oliva <aoliva at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>, Roland McGrath <roland at hack dot frob dot com>, libc-alpha <libc-alpha at sourceware dot org>
- Date: Sat, 1 Feb 2014 02:22:25 +0000
- Subject: Re: Release branch maintenance - Was: glibc 2.19 status?
- Authentication-results: sourceware.org; auth=none
- References: <52E649BF dot 5020400 at archlinux dot org> <20140128205657 dot 16DBA74438 at topped-with-meat dot com> <52E9DEB7 dot 4000709 at redhat dot com> <52E9E84F dot 50907 at redhat dot com> <52EA682D dot 90900 at archlinux dot org> <ormwid428y dot fsf at livre dot home> <Pine dot LNX dot 4 dot 64 dot 1401302131080 dot 12540 at digraph dot polyomino dot org dot uk> <20140131032418 dot GK2149 at spoyarek dot pnq dot redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1401311709310 dot 26476 at digraph dot polyomino dot org dot uk> <CAAHN_R2r6jiHWwj2HGDS-sruGewKEMmeQkAS9PXqZtOS95gKAw at mail dot gmail dot com> <52EC58E6 dot 6060702 at archlinux dot org>
On Sat, 1 Feb 2014, Allan McRae wrote:
> I'd like to have it set up so that the only thing the release branch
> maintainer needs to do is decide when to cut a new release. To achieve
> that, I'd like the distro maintainers to take any patch they pull from
> master into their package and commit it onto the relevant release
> branch. That way, the release branch reflects actual usage of that
I'm not sure about "any patch". Any bug-fix patch, probably, but there
may well be cases where one distribution has a use for backporting a new
feature from master and another doesn't want that feature backported.
--
Joseph S. Myers
joseph@codesourcery.com