"Carlos O'Donell" <[email protected]> writes: > On Mon, Aug 17, 2015 at 4:34 PM, Aurelien Jarno <[email protected]> wrote: >>> So this is IMO, the wrong thing to do. You should push the patch into >>> upstream 2.19 stable and rebase instead of keeping the patch in debian >>> svn. Given the patch is already in upstream master it is OK to commit >>> to 2.19 stable, and post to libc-stable stating you checked in this >>> fix. That way debian gets broader testing of the patches we are using >>> instead of the narrower "just debian" users. >> >> If it is fine to push this kind of patch in this branch, I would >> certainly do that. I also backported for debian patch b0a3c164. Would >> it be possible to also push it to the branch? > > If the patch doesn't change API/ABI, and it was accepted for master, > then it's perfectly acceptable to push to 2.19 stable branch.
Patch pushed to release/2.19.master as commit 980a63b3. -- Tulio Magno
