![]() g script, you do not need to worry about git submodule update. ![]() Once your submodule patch is merged, you can delete 'my_branch':īy using the. ![]() so that everybody will see the change at their next. On the gerrit side, when your patch is reviewed and submitted, gerrit will automatically create a commit on core to reflect the change in. Git push origin my_branch:refs/for/master Then push them to Gerrit from within the submodule directory: If you want to create a new change, create a new branch:Įdit the submodule's files and commit your changes inside the submodule directory. If the working submodule is helpcontent2, you should set help in place of. Git remote set-url -push origin ssh://logerrit/ This means that the checked-out commit - which is the one that the super-project (core) needs - is not associated with a local branch name.ĭon't forget to add a correct pushurl for the you are working on or you will not be able to commit. If you decide to manually clone a submodule, run this command after the clone is completed:īy default your submodule repository is in a state called 'detached HEAD'. The mentioned options fetch translations and help respectively. The recommended way to get submodules is to simply use autogen options like -with-lang= and -with-help=. That will reset the submodule to the commit it should be on according to core's information, and git status after that should not contain any reference to submodules. " to discard changes in working directory) If, when you do git status, you see something like If you are working on core only the submodules should track where they need to be based on the commit you are in in core.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |