Subject: Re: [boost] Git Modularization Review no vote heads-up
From: Dave Abrahams (dave_at_[hidden])
Date: 2013-05-22 01:30:10
on Tue May 21 2013, Vladimir Prus <ghost-AT-cs.msu.su> wrote:
> On 21.05.2013 01:21, BjÃ¸rn Roald wrote:
>> do you have a plan for how the top level scripts can work in both the
>> svn and the git environments prior to transition if you change
>> tools/build/v2 to tools/build?
> Even with my limited bash-fu, that is perfectly doable.
>>>> > >Which one do you prefer?
>>> >Nevertheless +1 for "tools/build" from my side if this works smoothly.
>> I propose to keep tools/build/v2 until all work is transitioned to git.
>> Then moving content of tools/build/v2 to tools/build is simple within
>> build submodule repository and the corresponding boost meta repository
>> can have modified top level scripts.
> To be honest, I don't trust git move (or lack thereof)
Well, there's nothing really we can do about that lack of trust. It's a
simple matter to move files in Git.
> and not really looking forward to spending an evening with company of
> 'git filter-branch'.
Why do you want to revise history?
> If an infrastructure for svn to git conversion is already developed,
> why not create the layout that is right?
How do you define "right?"
-- Dave Abrahams
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk