-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update protocol submodule to master branch from #p27 #47
Comments
I think it's done (it was a few mins after the main repo....)? pls confirm it all builds once both masters are pulled.... |
subrepos - bahh... trying to fix it now! |
pls check again. all should be good now. |
@btsimonh Everything built successfully. |
hmm... not seeing that through github or sourcetree.... |
bipropellant Cloning with reccursive submodules using gitbash, then adding all repos to github desktop. |
ok, I'll try a small mod on each and commit from github, change to readme maybe. one moment. |
In the meantime I am trying to clone on Sourcetree |
Well, detached head is "ok" when working with submodule. A submodule does not reference a branch or head, it references a single commit. This way you can make sure that the "main" repo decides which commit is ok. You can open git in your submodule folder and checkout the correct branch. This way the head shouldnt be detached anymore. |
@btsimonh It is now synced. Head is now synced upon cloning. |
@btsimonh, maybe you can update the Travis link in Readme to point to the bipropellant build check. At the moment it links to my fork Travis build. |
done |
I use sourcetree for all my windows git operations; it's not perfect for submodules, but I'm kind of getting used to it :). |
I gave up on using a fancy GUI for git. Just using the built in functions from vscode and git bash. |
@btsimonh Are you working to update protocol submodule? I am just trying to remind you in case you may forget.
The text was updated successfully, but these errors were encountered: