soliaround.blogg.se

1. #Update git submodule to latest commit update#
2. #Update git submodule to latest commit Patch#
3. #Update git submodule to latest commit code#

Use thereof is explained in our trademark policy (see Project:Copyrights for details). Their respective logos and icons are also subject to international copyright laws. "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries.

#Update git submodule to latest commit code#

This does not include the source code of LibreOffice, which is licensed under the GNU Lesser General Public License ( LGPLv3).

#Update git submodule to latest commit update#

If you are only cloning the submodules repo and gerrit complains about missing Change-Ids you can get the commit hook that adds the Change-ID by running this in the core directory:Īfter that use git commit -amend to update the commit msg and let git add the Change-ID. If you want to be creative, good for you, but then do not whine, if you shoot yourself in the foot. The advice is: stick to the one described here. There are of course other workflows that one can use, and plenty of other situations one can drive oneself into. This is not a problem for anyone else because the commit on core is always _after_ the commit on the submodules, so anyone else who pulls will not have your submodule commit before core knows about it. Note: if you are not pulling from, but from freedesktop for example, it may take a minute before a pull from core will get you the automatic commit created on core by gerrit. g script, you do not need to worry about git submodule update.

#Update git submodule to latest commit Patch#

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.