Boost logo

Boost :

Subject: [boost] mpl_core (Was: New dependency report)
From: Peter Dimov (lists_at_[hidden])
Date: 2014-06-08 09:54:07

Andrey Semashev wrote:

> Eyes are afraid, hands are doing. :) Here is my first take on this:

Thanks for doing this work.

Did you run the MPL tests on the new structure? (And if so, how - I'd like
to do the same.)

I think that in this case a better way to move the files into the new repo
will be to clone mpl into mpl_core and then 'git rm' the extra files. This
will likely preserve the history better, and it has the additional advantage
that you can at a later date move another file by just undeleting it.

Assuming that the tests are fine, I wonder what is the best way to proceed
from here.

Do people have objections to splitting these headers into a new submodule,

My initial thought is that we can create the new submodule on a feature
branch in the superproject, so as to not affect develop and master at this
time. The feature branch will not automatically pick up any further
'develop' changes in other modules, but that's probably not a problem. (The
changes to the existing MPL module will need to also be done on a branch, of

Boost list run by bdawes at, gregod at, cpdaniel at, john at