Re: [boost] Git Modularization Ready for Review

Subject: Re: [boost] Git Modularization Ready for Review
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-05-20 01:58:33

on Fri May 17 2013, Vladimir Prus <ghost-AT-cs.msu.su> wrote:

> On 14.05.2013 19:13, Daniel Pfeifer wrote:
>> 2013/5/13 Jürgen Hunold <jhunold_at_gmx.eu>
>>
>>> Hi Dave,
>>>
>>> On Saturday, 4. May 2013 12:08:22 Dave Abrahams wrote:
>
>>>> Hi All,
>>>>
>>>> After substantial work, including massive changes by me and Daniel
>>>> Pfeifer to KDE's svn->Git conversion tool, we have captured every Boost
>>>> SVN commit in a Git repository.
>>>
>>> Thanks for the work. Having done CVS -> svn myself, I really appreciate
>>> this.
>>>
>>>> You can view the results at
>>>>
>>>>      http://github.com/boostorg
>>>>      http://bitbucket.org/boostorg
>>>
>>> I have some questions concerning the Boost.Build conversion.
>>>
>>> The repository at
>>>
>>> https://github.com/boostorg/build
>>>
>>> contains a "buildv2" directory containing the Boost.Build .jam files and
>>> "jamsrc" directory containing the c sources.
>>>
>>
>> It seems the path seperators got lost. I think I fixed that problem, the
>> conversion is currently rerunning.
>
> It looks better now, but the root of the repo has 'build', which has 'v2',
> which has actual content. Can we actually have content of 'v2' at the top
> level?

We could, but that leaves open some questions:

1. What does history look like?  At some point, there's the v1 code at
   the top level.  Decide how you want those branches and commits
   distributed, and we can set it up.

2. Will this break scripts and other tools that invoke bjam?

-- 
Dave Abrahams