Boost logo

Boost :

Subject: Re: [boost] [git] Mercurial?
From: Joel de Guzman (joel_at_[hidden])
Date: 2012-03-27 07:15:54

On 3/27/2012 5:58 PM, Stephan Menzel wrote:
> git-svn specifically mentions that usage as being not supported. Two
> way svn syncs with changes on both ends are a no-go. I have tried that
> in the past and it didn't work out. Which means: Challenge not
> accepted! ;-)
> I have substantial experience with transistions like that in several
> projects in my past and I have the strong opinion that either you do
> it right or you don't do it at all. Any compromise along the git-svn
> lines except an initial export is bogus.
> As I said, it would have been nice, but existing sentiment forbids
> chasing that any further. The boost community should just accept this
> as consens and be done with it.

On 3/27/2012 5:54 PM, Philippe Vaucher wrote:

> To do that you first need to split the current repository where each lib
> has its own repository... making point 2 impossible or just too painful.
> Your workflow would be possible in a simple manner once we moved to git/hg
> where each lib has its own repository, which would be better imho (have
> lib-specific history instead of history from all the libs).

Ok, so if it can't be done with git-svn. Is there no other way
to do it then?

What you guys want is for the whole of Boost to migrate en-masse
to Git because it's the Git way? All or nothing? In one fell swoop?

I'm willing to migrate. I appreciate the benefits of a DVCS. I
can convince my fellow Spirit/Phoenix/Fusion devs to migrate.
But if you are telling me that I also have to convince all
the other Boost libraries to migrate en-masse, then that
is simply absurd!


Joel de Guzman

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