|
Boost : |
Subject: Re: [boost] [git] Near future.. How do we deal with git-native libraries?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2013-12-09 13:15:22
On Sat, Dec 7, 2013 at 5:54 PM, 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.
>
+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
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk