Subject: Re: [boost] [git] How to create a new submodule from existing submodule components?
From: Peter A. Bigot (pab_at_[hidden])
Date: 2014-01-02 11:52:42
On 01/02/2014 10:19 AM, Beman Dawes wrote:
> In that discussion, Peter wrote:
>> Hi everyone,
>> As a first step of moving Boost.Assert out of Utility and into its
>> own submodule, I've extracted its files (along with the history)
>> into a test repository of mine:
>> If you consider its contents acceptable, please let me know what
>> should the procedure be for moving this repository into boostorg
>> and making it a proper submodule.
> I've take the liberty of moving this discussion to the main list for
> wider input on three questions. Please respond on this thread to the
> question asked in the subject line, and comment on the Proposed
> assert submodule and Super-project workflow on their threads.
Am I correct in understanding that the purpose of this thread is not to
solicit instructions for how to extract a subtree with history into a
separate git repository, but rather what consensus and requirements are
to be applied to adding a new module and removing its functionality from
Is this not simply a matter of simultaneously applying existing
processes for consenting to a major change in an existing library and
accepting a new library into Boost?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk