Boost logo

Boost :

Subject: Re: [boost] [Boost.Sync] no master branch?
From: Eric Niebler (eniebler_at_[hidden])
Date: 2014-01-15 12:08:36

On 1/15/2014 6:10 AM, Tim Blechmann wrote:
>>>> What is Boost.Sync and why doesn't its repository have a master branch?
>>> That library is a split of Boost.Thread that only contains synchronization
>>> primitives. It's in an early development stage and not yet released, that's
>>> why it has no master.
>> If it is an "early development stage", why is it in boostorg at all? Seems
>> like it should be in the developer's own GitHub account.
> it was in trunk, but not in release. therefore it has a develop branch,
> but no master. compare [1]. the functionality is not exactly new, but
> broken out of boost.thread with some additions.
> tim
> [1]

Can you please explain the purpose of splitting these libraries? The
only reason given in that discussion is, "For example, one of the
benefits I'd like to achieve with this is that synchronization
primitives should become decoupled from the timing libraries.":

Why is that desirable? Is that it?

As a practical matter, the sync repo should not be in boostorg until it
has a master branch. I discovered this anomaly by trying to check out
every repo in the master branch with this git command:

> git submodule foreach git checkout master

That command fails today because of sync.

Eric Niebler

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