|
Boost : |
Subject: Re: [boost] El Capitan issues (Was: [1.61] Two weeks remaining for new libraries and breaking changes)
From: Robert Ramey (ramey_at_[hidden])
Date: 2016-02-17 11:50:07
On 2/17/16 7:10 AM, Steven Watanabe wrote:
> AMDG
>
> On 02/17/2016 01:25 AM, Robert Ramey wrote:
>> On 2/16/16 11:30 PM, Andrey Semashev wrote:
>>>
>>> Just recently I've had another case of synchronized update of multiple
>>> repositories on develop.
>>>
>>> https://github.com/boostorg/winapi/pull/20
>>> https://github.com/boostorg/dll/pull/7
>>> https://github.com/boostorg/dll/pull/8
>>>
>>> Such situations appear more often than you think.
>>
>> another case? Looking at this particular case I think "exceedingly
>> rare" is still an accurate characterization.
>>
>
> With the example I posted, that makes two
> of your "exceedingly rare" cases in the
> last week.
All these cases relate to two coupled libraries. Regardless of
questions about the wisdom and/or avoidability of such coupling,
these examples aren't counter examples to my main point.
In these examples, the correct action would be to checkout both
coupled libraries, switch both to develop branch and update and
run tests on those two (or three...) while leaving the other
125 libraries in master. Of course in this case they have to pushed
and merged as a pair - because they're coupled. But it doesn't
argue against my suggestion.
>
> In Christ,
> Steven Watanabe
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk