Re: [boost] [git] Near future.. How do we deal with git-native libraries?

Subject: Re: [boost] [git] Near future.. How do we deal with git-native libraries?
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-12-08 12:44:41

Daniel James <daniel_at_[hidden]> writes:

> On 7 December 2013 22:54, Dave Abrahams <dave_at_[hidden]> wrote:
>> Daniel James <daniel_at_[hidden]> writes:
>>
>>> On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ <joaquin_at_[hidden]> wrote:
>>>>
>>>> I understand this is
>>>>
>>>> https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96da2bd
>>>>
>>>> Excuse my ignorance but: does this mean syncing between the master project and
>>>> submodules need be done manually? I was assuming that somehow updates to a
>>>> submodule automatically propagate to checkouts of the master project.
>>>
>>> Currently it needs to be done manually. Eventually it should be
>>> scripted, hopefully from a git hook so that it's pretty fast. There's
>>> some dispute about how the changes should be propagated to the main
>>> module.
>>
>> IMO boostorg/boost's master branch shouldn't get updated to a state X
>> until X passes regression testing.
>
> Is this something you're willing to automate? I don't think anyone
> will want to do that manually.

It's easy enough to do manually, IMO.  It would certainly be better to
have it automated.  I don't have time to work on Boost for the
forseeable future, so no, I won't be automating it.