Re: [boost] Git: maintaining super-project

Subject: Re: [boost] Git: maintaining super-project
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2013-12-04 06:31:35

On Wed, Dec 4, 2013 at 3:14 PM, Daniel James <daniel_at_[hidden]> wrote:
> On 4 December 2013 09:53, Andrey Semashev <andrey.semashev_at_[hidden]> wrote:
>> On Wed, Dec 4, 2013 at 1:13 PM, Daniel James <daniel_at_[hidden]> wrote:
>>> On 4 December 2013 07:27, Cox, Michael <mhcox_at_[hidden]> wrote:
>>>> The following should get you what your asking for, if I understand you
>>>> correctly:
>>>>
>>>> git clone --recursive -b develop https://github.com/boostorg/boost
>>>>
>>>> git submodule foreach git checkout develop
>>>
>>> Most developers won't do this, they'll be using the master branch of
>>> the super project, and only checking out develop for the modules
>>> they're concerned with.
>>>
>>> Although our testing system won't be doing that at first, and probably
>>> not for some time. Which is a problem.
>>
>> As long as the testing is done against develop or master branch of
>> *all* modules I don't see why individual developers should be doing
>> that.
>
> Maybe you should try looking at older threads where this was discussed.

I remember the discussions but still stand by my words. There's no
point in testing locally something that will possibly break in the
official test system.