On 7 December 2013 22:54, Dave Abrahams wrote:

Daniel James writes:

...

On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ wrote:

...

I understand this is

https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...

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.

On Sat, Dec 7, 2013 at 5:54 PM, Dave Abrahams wrote:

Daniel James writes:

...

On 5 December 2013 08:23, JOAQUIN M. LOPEZ MUÑOZ wrote:

...

I understand this is

https://github.com/boostorg/boost/commit/66b6e0b0dcff397010815624ce02c1d1c96...

...

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.

+1 We aren't there yet, although the conversion to git and modular boost has put us a lot closer than we were. Daniel is, IIUC, trying to address the question of what we do right now. --Beman