Re: [boost] [Git] Documentation for Git and Modular Boost conversion

Subject: Re: [boost] [Git] Documentation for Git and Modular Boost conversion
From: Dave Abrahams (dave_at_[hidden])
Date: 2012-12-15 21:42:37

on Mon Dec 10 2012, Beman Dawes <bdawes-AT-acm.org> wrote:

> On Sat, Dec 8, 2012 at 8:43 PM, Julian Gonggrijp <j.gonggrijp_at_[hidden]> wrote:
>
>> Browsing through the wiki pages linked from that section, a few things
>> caught my attention.
>>
>>
>> wiki/ModCvtSvn2Git [1] states
>>
>>> Each individual Boost library's public repository will contain a
>>> single branch, "master", that corresponds to branches/release in
>>> Subversion.
>>
>> As I seemed to recall that the modularized Boost would adopt GitFlow,
>
> Yes, that's the plan.
>
>> I was surprised by the suggestion that a library's public repository
>> would not be allowed (or at least not required) to have a "develop"
>> branch corresponding to the Subversion "trunk".
>
> Hum... That's too narrow an interpretation. I've added wording to
> distinguish between initial state at conversion and then the ongoing
> workwflow

I'm sorry, but I have always intended to do what Julian thought: produce
an initial "develop" branch corresponding to "trunk" along with
"master."

-- 
Dave Abrahams
BoostPro Computing                  Software Development        Training
http://www.boostpro.com             Clang/LLVM/EDG Compilers  C++  Boost