git submodules. Detached state vs master










0















Lets say i have two repos R1 and R2 which are using one common submodule.



When time comes to build any of them, i see two possible ways



  • Keeping submodule in detached state on a specific commit

  • Always updating it to latest change using $git pull

Which practice is the best and most safe?



Thanks!










share|improve this question


























    0















    Lets say i have two repos R1 and R2 which are using one common submodule.



    When time comes to build any of them, i see two possible ways



    • Keeping submodule in detached state on a specific commit

    • Always updating it to latest change using $git pull

    Which practice is the best and most safe?



    Thanks!










    share|improve this question
























      0












      0








      0








      Lets say i have two repos R1 and R2 which are using one common submodule.



      When time comes to build any of them, i see two possible ways



      • Keeping submodule in detached state on a specific commit

      • Always updating it to latest change using $git pull

      Which practice is the best and most safe?



      Thanks!










      share|improve this question














      Lets say i have two repos R1 and R2 which are using one common submodule.



      When time comes to build any of them, i see two possible ways



      • Keeping submodule in detached state on a specific commit

      • Always updating it to latest change using $git pull

      Which practice is the best and most safe?



      Thanks!







      git git-submodules






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 12:10









      Frolov AlexFrolov Alex

      41




      41






















          1 Answer
          1






          active

          oldest

          votes


















          2














          Both repositories have an independent reference to a commit in the submodule repository. If you want to change the commit, you have to commit the changed submodule commit id in the parent repository.




          Keeping submodule in detached state on a specific commit




          There is always a certain commit checked out in a submodule. There might be some branch pointing to that commit, or there might not be. All the parent repository knows is the id of the commit that should currently be checked out.




          Always updating it to latest change using $git pull




          It's entirely up to you when you do this. It's usually done when the parent repository needs updated features from the submodule, or important bugfixes have been made. Otherwise, there is no need to update.



          I advise to do some further reading on submodules, for example in the pro git book.






          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319225%2fgit-submodules-detached-state-vs-master%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Both repositories have an independent reference to a commit in the submodule repository. If you want to change the commit, you have to commit the changed submodule commit id in the parent repository.




            Keeping submodule in detached state on a specific commit




            There is always a certain commit checked out in a submodule. There might be some branch pointing to that commit, or there might not be. All the parent repository knows is the id of the commit that should currently be checked out.




            Always updating it to latest change using $git pull




            It's entirely up to you when you do this. It's usually done when the parent repository needs updated features from the submodule, or important bugfixes have been made. Otherwise, there is no need to update.



            I advise to do some further reading on submodules, for example in the pro git book.






            share|improve this answer



























              2














              Both repositories have an independent reference to a commit in the submodule repository. If you want to change the commit, you have to commit the changed submodule commit id in the parent repository.




              Keeping submodule in detached state on a specific commit




              There is always a certain commit checked out in a submodule. There might be some branch pointing to that commit, or there might not be. All the parent repository knows is the id of the commit that should currently be checked out.




              Always updating it to latest change using $git pull




              It's entirely up to you when you do this. It's usually done when the parent repository needs updated features from the submodule, or important bugfixes have been made. Otherwise, there is no need to update.



              I advise to do some further reading on submodules, for example in the pro git book.






              share|improve this answer

























                2












                2








                2







                Both repositories have an independent reference to a commit in the submodule repository. If you want to change the commit, you have to commit the changed submodule commit id in the parent repository.




                Keeping submodule in detached state on a specific commit




                There is always a certain commit checked out in a submodule. There might be some branch pointing to that commit, or there might not be. All the parent repository knows is the id of the commit that should currently be checked out.




                Always updating it to latest change using $git pull




                It's entirely up to you when you do this. It's usually done when the parent repository needs updated features from the submodule, or important bugfixes have been made. Otherwise, there is no need to update.



                I advise to do some further reading on submodules, for example in the pro git book.






                share|improve this answer













                Both repositories have an independent reference to a commit in the submodule repository. If you want to change the commit, you have to commit the changed submodule commit id in the parent repository.




                Keeping submodule in detached state on a specific commit




                There is always a certain commit checked out in a submodule. There might be some branch pointing to that commit, or there might not be. All the parent repository knows is the id of the commit that should currently be checked out.




                Always updating it to latest change using $git pull




                It's entirely up to you when you do this. It's usually done when the parent repository needs updated features from the submodule, or important bugfixes have been made. Otherwise, there is no need to update.



                I advise to do some further reading on submodules, for example in the pro git book.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 15 '18 at 12:27









                kowskykowsky

                3,3811425




                3,3811425





























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53319225%2fgit-submodules-detached-state-vs-master%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    這個網誌中的熱門文章

                    What does pagestruct do in Eviews?

                    Dutch intervention in Lombok and Karangasem

                    Channel Islands