Closed naufraghi closed 11 years ago
Thanks naufraghi. Before I merge your pull-request, what is your opinion on merging new work first into the develop branch, and then merge the develop branch into the master branch for releases (so the master branch always reflects the last stable release). It seems if the develop branch will be left out of date since the pull request merges into master. What do you think?
Ok, yes, something like http://nvie.com/posts/a-successful-git-branching-model/.
Perhaps we can explain better in the README file that master is the release/stable branch and that all the pull requests are supposed to be against develop (and reverse at least one arrow in the asciiart in Repository Structure).
I'm going to open a new pull request against the develop branch as soon as possible.
The previous ref was resulting in:
I resolved it following the "Inside, Out" part of this recipe: Git submodule head 'reference is not a tree' error