On Sun, Oct 9, 2016 at 1:36 PM, Vinnie Falco wrote:

On Sun, Oct 9, 2016 at 2:13 PM, Raffi Enficiaud wrote:

...

Fetched in submodule path 'libs/python', but it did not contain 0ca7db361b8a70540c5683ae3ba2219c3352f721. Direct fetching of that commit failed.

I can confirm that on a fresh clone of the boost superproject, these commands produce the same error: ``` git checkout aa407db3 git submodule init git submodule update libs/python ```

Beats me what's going on.. All I can say is: ain't submodules wonderful? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

On 10/09/16 22:56, András Kucsma wrote:

The commit is there, but it's not on any branch: https://github.com/boostorg/python/commit/0ca7db361b8a70540c5683ae3ba2219c33...

Since it's not connected to any branch or tag it's not cloned or fetched by default.

One thing that could've happened that boostorg/python master or develop branch was force pushed and this commit was removed.

Forced pushes has caused me headache in the past as well. Is there a way on GitHub to prohibit forced pushes to a certain branch?

On 10/10/16 00:22, Vinnie Falco wrote:

On Sun, Oct 9, 2016 at 5:20 PM, Andrey Semashev wrote:

...

Forced pushes has caused me headache in the past as well. Is there a way on GitHub to prohibit forced pushes to a certain branch?

Yes, the feature is called "Protected Branches" and detailed here: https://help.github.com/articles/about-protected-branches/

Looks perfect. Then it might be a good idea to mark master and develop as protected in all repos under boostorg.