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-24 01:00:07

On Thu, May 23, 2013 at 8:44 AM, Dave Abrahams <dave_at_[hidden]> wrote:

>
> on Thu May 23 2013, "Jürgen Hunold" <jhunold-AT-gmx.eu> wrote:
>
> > Dave wrote:
>
> I think that a one-to-one mapping like:
> >
> > repository build : common_branches
> > {
> >   submodule of "boost" : "tools/build";
> >   content
> >   {
> >     "tools/build/" ;
> >   }
> >
> > is the way to go now. If something goes wrong,
>
> It will, because we'd no longer be catching tools/jam throughout
> history.  That will cause modularization to fail.
>
> > please put "tools/jam/" somewhere else.
>
> Yeah, that's not specific enough.  What is "somewhere else?"
>

branch = historical
path = "jam/"

We could put it in the "engine" /v2/engine/ subdirectory of the build
> repository, but that would be utterly inaccurate for older history.  We
> can also have it move into /v2/engine from somewhere else (as it
> actually does in SVN), but again, what is "somewhere else?"
>
> ...and—just checking—do you speak for the Boost.Build project, or is
> Volodya likely to countermand your requests?
>
> > Btw. would
> >
> > repository build : common_branches
> > {
> >   submodule of "boost" : "tools/build";
> >   content
> >   {
> >     "tools/build/v2" ;
> >   }
> >
> > be the right way to move v2 one directory up?
>
> That would move the contents of v2 to the top level of the build repo,
> but it would also drop all the commits that historically went directly
> into tools/build/ (Boost.Build v1 mostly).  Like I said, we need
> decisions about where *everything* that was in Boost.Build—throughout
> history—belongs.
>

Anything before v2 existed should go to:

branch = historical
path = "build/"

Or more descriptive..

1. Put anything that ever existed in the current build/v2/* files at the
root of the new build repo.
2. Put anything else in some form of "historical" branch using the path
from "boost-root/" as the path in the new repo. (I don't care that much
about the actual branch names other than to tell that they are there only
as history).

But since I don't know git sufficiently.. I don't know if that's
practically possible. Specifically I don't know if one can follow history
back across branches. if it's not possible then I would say change #2 above
to:

2. Put anything else at historical/jam, and historical/build in whatever
branches you have now.

I'll let Volodya and Jürgen comment and concur as they see fit :-)

-- 
-- 
-- 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