Subject: Re: [boost] Fwd: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1)
From: Robert Ramey (ramey_at_[hidden])
Date: 2015-04-10 12:06:51
Beman Dawes wrote
> While I understand how a continuous integration framework might only merge
> to master when develop tests are passing satisfactorily, I'm not aware of
> any way to prevent breaking merges with our current testing approach.
I think there is a way to "lock" a branch so that no one can push a merged
This looks like it might be useful to us - but don't take my word for it as
I'm a git noob
-- View this message in context: http://boost.2283326.n4.nabble.com/Fwd-Boost-Python-build-error-in-1-58-RC1-2-and-3-OK-in-Beta-1-tp4674304p4674385.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk