Re: [boost] [iterator, test] pa-risc HP-UX compatibility - patches for iterator and test libraries.

Jurko Gospodnetic wrote:
I'm attaching two patches - one for the Boost test and one for the Boost iterator library to make them compatible with HP-UX PA_RISC 11.11 system headers. [...] Could someone please apply them? And could they be applied to the 1.35 branch as well?
If there are no objections, I can apply the patches to trunk and the release branch. Thanks, Boris

Boris Gubenko wrote:
Jurko Gospodnetic wrote:
I'm attaching two patches - one for the Boost test and one for the Boost iterator library to make them compatible with HP-UX PA_RISC 11.11 system headers. [...] Could someone please apply them? And could they be applied to the 1.35 branch as well?
If there are no objections, I can apply the patches to trunk and the release branch.
Best practice is to apply first to trunk, then wait until trunk regression tests cycle, and look at those results. The point being to be *very* sure patches to the release branch don't break things. Thanks, --Beman

Beman Dawes wrote:
Boris Gubenko wrote:
If there are no objections, I can apply the patches to trunk and the release branch.
Best practice is to apply first to trunk, then wait until trunk regression tests cycle, and look at those results.
Absolutely! I'll also conditionalize the fix for HP-UX only: even though the change seems to be safe, no other platform needs it. Thanks, Boris ----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: <boost@lists.boost.org> Sent: Thursday, December 13, 2007 11:14 AM Subject: Re: [boost] [iterator, test] pa-risc HP-UX compatibility - patches for iterator and test libraries.
Boris Gubenko wrote:
Jurko Gospodnetic wrote:
I'm attaching two patches - one for the Boost test and one for the Boost iterator library to make them compatible with HP-UX PA_RISC 11.11 system headers. [...] Could someone please apply them? And could they be applied to the 1.35 branch as well?
If there are no objections, I can apply the patches to trunk and the release branch.
Best practice is to apply first to trunk, then wait until trunk regression tests cycle, and look at those results.
The point being to be *very* sure patches to the release branch don't break things.
Thanks,
--Beman _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (2)
-
Beman Dawes
-
Boris Gubenko