Re: [boost] Git Modularization Review no vote heads-up

Subject: Re: [boost] Git Modularization Review no vote heads-up
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2013-05-26 15:49:18

On Sun, May 26, 2013 at 2:42 PM, Bjørn Roald <bjorn_at_[hidden]> wrote:

> On Sun, 2013-05-26 at 21:25 +0200, Daniel Pfeifer wrote:
> > 2013/5/26 Jürgen Hunold <jhunold_at_gmx.eu>
> >
> > > Hi Bjørn,
> > >
> > > On Sunday, 26. May 2013 13:01:18 Bjørn Roald wrote:
> > > > On Sat, 2013-05-25 at 23:00 +0200, Daniel Pfeifer wrote:
> > > > > This patch does not apply to the complete history. I added the
> > > following
> > > > > command instead:
> > > > >
> > > > > $ git filter-branch --tree-filter "find . -type f -maxdepth 1 -exec
> > > sed -i
> > > > > -e 's|build[/\\]v2|build|g' {} \;"
> > > >
> > > > Nice - composing with tools the unix way certainly has it's
> strengths.
> > >
> > > Definetely ;-)
> >
> >
> > It is also pretty slow. Rewriting Boost's history that way takes about 4
> > hours.
> >
> > I changed the mapping accoring to Bjørn's suggestion.
> >
> > tools/build/v2 will end up in tools/build/v2. I think that makes most
> sense.
>
> Err  -- although I still support my suggestion, boost build maintainers
> seems to differ and they have more of a say here than I do and I
> willingly yield. I feel like I am just getting in the way of progress
> here.
>

I was about to mention something.. So thanks for the comment :-)

But if life is such a pain with squashing the v2 subtree.. I guess the b2
maintainers will just have to squash the v2 at the source.. I.e. make the
current Boost svn structure be tools/build/* moving all files and changing
the scripts.. and especially painful adjusting the testing regression
scripts. Which may impact the upcoming release schedules.

-- 
-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo