On Thursday 15 January 2015 21:47:00 Peter Dimov wrote:
The module libs/sync has no master branch, why?
Because it has not been released yet. Shame on me, I promised to finish things left to do in Boost.Sync long time ago but never got around to it. But I will. I promise. :)
Andrey Semashev wrote:
On Thursday 15 January 2015 21:47:00 Peter Dimov wrote:
The module libs/sync has no master branch, why?
Because it has not been released yet.
I know, but that doesn't seem a reason to not have a master branch, I think. The module does not exist on the master branch of the superproject, so it will not be released.
On Thursday 15 January 2015 22:55:13 Peter Dimov wrote:
Andrey Semashev wrote:
On Thursday 15 January 2015 21:47:00 Peter Dimov wrote:
The module libs/sync has no master branch, why?
Because it has not been released yet.
I know, but that doesn't seem a reason to not have a master branch, I think. The module does not exist on the master branch of the superproject, so it will not be released.
What's the point in having the master branch then?
Andrey Semashev wrote:
What's the point in having the master branch then?
The specific problem I was having was that any "git submodule foreach" that references "master" failed at libs/sync. But in general, I'd think that the point of having the master branch for Sync would be the same as for the other libraries; look at the develop regression tests, if they pass, merge to master.
On Friday 16 January 2015 00:54:21 Peter Dimov wrote:
Andrey Semashev wrote:
What's the point in having the master branch then?
The specific problem I was having was that any "git submodule foreach" that references "master" failed at libs/sync.
Was that because your superproject's develop branch had been checked out when you ran the commands?
But in general, I'd think that the point of having the master branch for Sync would be the same as for the other libraries; look at the develop regression tests, if they pass, merge to master.
Since the master branch of the superproject does not have Sync, the tests would not run on master, as I understand. I could create master. It's just I would have to do merging then, which is kind of pointless since there really is just develop at this stage.
On Friday 16 January 2015 02:37:56 you wrote:
On Friday 16 January 2015 00:54:21 Peter Dimov wrote:
Andrey Semashev wrote:
What's the point in having the master branch then?
The specific problem I was having was that any "git submodule foreach" that references "master" failed at libs/sync.
Was that because your superproject's develop branch had been checked out when you ran the commands?
But in general, I'd think that the point of having the master branch for Sync would be the same as for the other libraries; look at the develop regression tests, if they pass, merge to master.
Since the master branch of the superproject does not have Sync, the tests would not run on master, as I understand.
I could create master. It's just I would have to do merging then, which is kind of pointless since there really is just develop at this stage.
Oh, and BTW, as I remember Sync relies on DateTime features in develop. I'm not sure if these features were merged to master.
participants (2)
-
Andrey Semashev -
Peter Dimov