Subject: Re: [boost] [git] How to create a new submodule from existing submodule components?
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-01-04 08:30:35
On Thu, Jan 2, 2014 at 11:52 AM, Peter A. Bigot <pab_at_[hidden]> wrote:
> 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:
> >> https://github.com/pdimov/assert
> >> 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
> another module?
I was interested in capturing instructions for extracting a subtree with
history so they can be documented for future reference.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk