The difference is:

- `git pull` will only update your submodule branch, but it can be any branch that you could have checked out yourself in that submodule repo.
- `git submodule update --remote` will only update the branch registered in the `.gitmodule`, and by default, you will end up with a detached HEAD, unless `--rebase` or `--merge` is specified or the key `submodule.$name.update` is set to `rebase`, `merge` or `none`.

In both cases, you still have to go back to the parent repo, add and commit the new submodule SHA1 reference.  
That is because in both instances, the SHA1 of the submodule changes, which means the **[gitlink][1]** ([special entry in the index][2] of the parent repo, named after to root folder of the submodule) must be added and committed.

A [`git submodule update --init --remote`][3] is like:

- [`git submodule init`][4]: to initialize (checkout) the submodules recorded in the index
- [`git submodule update --remote`][3]: to pull from the registered branch (or master by default), once the submodule has been initialized (checked out).


  [1]: https://stackoverflow.com/a/16581096/6309
  [2]: https://stackoverflow.com/a/19354410/6309
  [3]: https://git-scm.com/docs/git-submodule#Documentation/git-submodule.txt-update--init--remote-N--no-fetch--no-recommend-shallow-f--force--checkout--rebase--merge--referenceltrepositorygt--depthltdepthgt--recursive--jobsltngt--no-single-branch--ltpathgt82308203
  [4]: https://git-scm.com/docs/git-submodule#Documentation/git-submodule.txt-init--ltpathgt82308203

I have successfully built my Spring MVC project with `mvn clean package` by following [this tutorial][1].

Now I am trying to run the service with:

    mvn clean package &amp;&amp; java -jar target/gs-serving-web-content-0.1.0.jar

But I get this error:

**Failed to load Main-Class manifest attribute from
target/gs-serving-web-content-0.1.0.jar**

Am I missing something?


  [1]: http://spring.io/guides/gs/serving-web-content/

Failed to load Main-Class manifest attribute while running java -jar

I am using Ember.js with local-storage-adapter. I have a weird problem while updating records. 

I have a post and comments model with hasMany relationships:

    App.Post = DS.Model.extend({
        title: DS.attr(&#39;string&#39;),
        comments: DS.hasMany(&#39;comment&#39;, {
            async: true
        })
    });
    App.Comment = DS.Model.extend({
        message: DS.attr(&#39;string&#39;)
    });

These are my post and comments controllers:

    App.PostsController = Ember.ArrayController.extend({
        newTitle: &#39;&#39;,
        actions: {
            create: function() {
                var title = this.get(&#39;newTitle&#39;);
                var post = this.store.createRecord(&#39;post&#39;, {
                    title: title
                });
                this.set(&#39;newTitle&#39;, &#39;&#39;);
                post.save();
            }
        }
    });
    App.CommentsController = Ember.ArrayController.extend({
        needs: &quot;post&quot;,
        post: Ember.computed.alias(&quot;controllers.post.model&quot;),
        newMessage: &#39;&#39;,
        actions: {
            create: function() {
                var message = this.get(&#39;newMessage&#39;);
                var comment = this.store.createRecord(&#39;comment&#39;, {
                    message: message
                });
                var post = this.get(&#39;post&#39;);
                var comments = post.get(&#39;comments&#39;);
                if (comments.get(&#39;content&#39;) == null) comments.set(&#39;content&#39;, []);
                comments.pushObject(comment);
                comment.save();
                post.save();
            }
        }
    });

While creating records hasMany relations updated correctly. 

    {
        &quot;App.Post&quot;: {
            &quot;records&quot;: {
                &quot;0v66j&quot;: {
                    &quot;id&quot;: &quot;0v66j&quot;,
                    &quot;title&quot;: &quot;post1&quot;,
                    &quot;comments&quot;: [&quot;p31al&quot;, &quot;tgjtj&quot;]
                }
            }
        },
        &quot;App.Comment&quot;: {
            &quot;records&quot;: {
                &quot;p31al&quot;: {
                    &quot;id&quot;: &quot;p31al&quot;,
                    &quot;message&quot;: &quot;comment 1&quot;
                },
                &quot;tgjtj&quot;: {
                    &quot;id&quot;: &quot;tgjtj&quot;,
                    &quot;message&quot;: &quot;comment 2&quot;
                }
            }
        }
    }
The problem occured while editing post. The relationships are gone after editing  the post record. I did some searching and found this code:

    DS.JSONSerializer.reopen({
        serializeHasMany: function(record, json, relationship) {
            var key = relationship.key;
            var relationshipType = DS.RelationshipChange.determineRelationshipType(record.constructor, relationship);
            //  alert(relationshipType);
            if (relationshipType === &#39;manyToNone&#39; || relationshipType === &#39;manyToMany&#39; || relationshipType === &#39;manyToOne&#39;) {
                json[key] = Ember.get(record, key).mapBy(&#39;id&#39;);
                // TODO support for polymorphic manyToNone and manyToMany
                // relationships
            }
        }
    });

   
This did the trick and it worked fine. But now I have another problem. If I edit any other record, all the id references are replaced by whole object like this:

    {&quot;App.Post&quot;:{&quot;records&quot;:{&quot;0v66j&quot;:{&quot;id&quot;:&quot;0v66j&quot;,&quot;title&quot;:&quot;post2&quot;,&quot;comments&quot;:[**{&quot;message&quot;:&quot;comment 1&quot;},
    {&quot;message&quot;:&quot;comment 2&quot;}**]},&quot;8nihs&quot;:{&quot;id&quot;:&quot;8nihs&quot;,&quot;title&quot;:&quot;post3&quot;,&quot;comments&quot;:[&quot;b4v2b&quot;,&quot;dbki4&quot;]}}},
    &quot;App.Comment&quot;:{&quot;records&quot;:{&quot;p31al&quot;:{&quot;id&quot;:&quot;p31al&quot;,&quot;message&quot;:&quot;comment 1&quot;},&quot;tgjtj&quot;:{&quot;id&quot;:&quot;tgjtj&quot;,&quot;message&quot;:&quot;comment 2&quot;},
    &quot;b4v2b&quot;:{&quot;id&quot;:&quot;b4v2b&quot;,&quot;message&quot;:&quot;comments3&quot;},&quot;dbki4&quot;:{&quot;id&quot;:&quot;dbki4&quot;,
    &quot;message&quot;:&quot;comments4&quot;}}}}


Comment refrences should be **comments&quot;:[&quot;p31al&quot;,&quot;tgjtj&quot;]** like this. but the ids are replaced as &quot;comments&quot;:[**{&quot;message&quot;:&quot;comment 1&quot;},{&quot;message&quot;:&quot;comment 2&quot;}**]

Ember js - Hasmany relationships breaks after updating other tables

What is the difference between running 

    git submodule update --remote
vs 

    cd &lt;submodule directoy&gt;
    git pull

Assuming that the submodule was previously set to track some branch:

    git submodule add -b master [URL to Git repo]


git submodule update --remote vs git pull

What is the difference between running
<pre><code class="hljs language-sql">git submodule update --remote
</code></pre>
vs
<pre><code class="hljs language-bash">cd &#x3C;submodule directoy>
git pull
</code></pre>
Assuming that the submodule was previously set to track some branch:
<pre><code class="hljs language-css">git submodule add -b master [URL to Git repo]
</code></pre>

When I try to run previously working git commands, I get this:

    dyld: Symbol not found: _sqlite3_intarray_bind
      Referenced from: /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
      Expected in: /opt/local/lib/libsqlite3.dylib
     in /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    git: error: unable to locate xcodebuild, please make sure the path to the Xcode folder is set correctly!
    git: error: You can set the path to the Xcode folder using /usr/bin/xcode-select -switch

How can I fix this?

git error &quot;unable to locate xcodebuild&quot; after a fresh OS X Mavericks upgrade

I am working on a `MeteorIntegration` (feature) branch that is published. I did a `git push` assuming the push was going to the checked-out branch `MeteorIntegration`: 

And now I see the following on both `master` and `MeteorIntegration` branches. 

![github snap][1]

I read github documentation: [Closing a pull request][2] and [Tidying up Pull Requests][3] but that didn&#39;t help, possibly because I am not dealing with a pull request here?

**How do I get rid of this `compare &amp; pull request`?** 

  [1]: http://i.stack.imgur.com/8jEby.png
  [2]: https://help.github.com/articles/closing-a-pull-request
  [3]: https://help.github.com/articles/tidying-up-pull-requests

What is github &#39;compare &amp; pull request&#39;

I&#39;m trying to push a file to a git repo of a friend but errors on public key.

    git push origin testbranch
    Permission denied (publickey).
    fatal: Could not read from remote repository.

Where and how do we define public / private keys? 

`git remote -v` returns:

    origin	git@github.com:Sesamzaad/NET.git (fetch)
    origin	git@github.com:Sesamzaad/NET.git (push)

Any help is appreciated.

git push: permission denied (public key)

I have an existing Visual Studio project in my repository. I recently added a .gitignore file under my project and I assume that tells Git to ignore the files listed in the file. 

My problem is that all those files are already being tracked and as far as I know Git will not ignore a file that was already tracked before a rule was added to this file to ignore it.

It was suggested to use: `git rm --cached` and manually un-track them but that&#39;s going to take me forever to go through them one by one. 

I thought about deleting the repository and recreating it again but this time with .gitignore file present, but there must be a better way to do this.

Apply .gitignore on an existing repository already tracking large number of files

Is there a quick and easy way to open a git repository in SourceTree from the command line? 

I do a lot of git work from Terminal, but sometimes there&#39;s no replacement for a good history view/diff. Would love to be able to open without using bookmarks.



How do you open SourceTree from the command line?

I have a project that contains many submodules. I want to loop over each submodule with the following command:

`git submodule foreach npm install`

And I want the script to continue looping over each submodule even if one submodule returns an error (non zero return code). Currently, a non-zero return code from running this command in any submodule will cause git to stop looping over the remaining submodules.

Any recommendations on how to accomplish this?

Continue looping over submodules with the &quot;git submodule foreach&quot; command after a non-zero exit

As far as I know, if you add a submodule in git then it points to a certain commit in that submodule. 

Is there any way to see which commit a submodule is pointing at without checking it out?

How to see which commit a git submodule points at

I&#39;m actually trying to learn how to use git, including the `git submodule` subcommands.
I already set up a server on which I can host, push and pull git repositories by using SSH.
I created a main git repository &quot;Travail&quot; on this server in which I would like to put all my projects as submodules.

In my Travail repository, I already added a project of mine as a submodule at `tools/libft`:
I&#39;m able to develop this submodule, to push and to pull it.

But when I try to add another submodule (named fdf, from fdf.git on my server), I get the following issue :

    git submodule add ssh://XXX.XXX.XXX.XXX:XXXXX/opt/git/fdf.git projets/fdf
    
&gt;A git directory for &#39;projets/fdf&#39; is found locally with remote(s):
      origin	ssh://git@XXX.XXX.XXX.XXX:XXXXX/opt/git/fdf.git
    If you want to reuse this local git directory instead of cloning again from
      ssh://XXX.XXX.XXX.XXX:XXXXX/opt/git/fdf.git
    use the &#39;--force&#39; option. If the local git directory is not the correct repo 
    or you are unsure what this means choose another name with the &#39;--name&#39; option.

There is actually no subdirectory in `projets/`

I read on another thread that I should use `git submodule sync` or edit the .gitmodules file in which the URL to my submodule&#39;s origin repository could have changed.

But my .gitmodules file only contains the information about my first submodule (tools/libft), not about projets/fdf :

    [submodule &quot;tools/libft&quot;]
    	path = tools/libft
    	url = ssh://git@XXX.XXX.XXX.XXX:XXXXX/opt/git/libft.git

As a French student I could have missed something in the English documentation I have, but I searched and I really don&#39;t understand why I get this issue.

I would be glad if I would get a solution but just an explanation would be helpful too.

Git submodule add: &quot;a git directory is found locally&quot; issue

Someone please help me understand submodules in git. I know they are getting a lot of bashing around the internet but since I assume the git developers are smart people there must a reason for the current behavior - and maybe a way to work around my problem.

So, I have a project and some submodules. The project have different branches, like:

 * MyApp_version2
 * MyApp_version3
 * MyApp_version4
 * MyApp_liteversion
 * MyApp_development

My submodules doesn&#39;t update that often (maybe once a week) so I&#39;m fine with them [not being attached to the head of the submodule repository automatically](https://stackoverflow.com/questions/1979167/git-submodule-update).

However, when I check out an old branch - because I need to fix a bug in an old version of the software - I also need to update the submodules.

Why do I need to do this?

I would expect git to work like svn. When I commit my work in my main repo I would expect git to think something along these lines: &quot;OK, he wants to commit his work now. I can see the submodules are currently at revision abc so when he at some point in the future get&#39;s back to this commit he probably wants the submodules at the same revision again.&quot;

I can not see a single case where you would want the submodules to stay at the current revision while you go back 3 years in your main repository. However, there must be a reason for this implementation, right?

I would really like to hear if any of you know the thoughts behind this, but in any case I would really like a solution. Is there a way to tell git: &quot;I want to commit this work with these submodules. If I at some point go back to this state I want the submodules to be checked out at the correct version as well.&quot;


**Example for clarification**

My main repository is an application which needs to use SSL, and I find a SSL library (libSSL) I add as a submodule.

On Oct. 31 2010 I create a commit in my main repository (2fd4e1) while the submodule points to libSSL version 3 (c67a2d).

Time passes, libSSl gets updated to version 34, I adapt my code, life it good.

On May 14 2013 I create a new commit (28fced) and submodule points to the most recent version of libSSL (849ee1).

However, if I check out 2fd4e1 my submodule will stay at 849ee1 even though the original commit was created with c67a2d. Git knows I made the original commit with c67a2d and I don&#39;t see how you could possibly want a another submodule than the one the original commit was created with.

Why doesn&#39;t `git checkout` automatically do `git submodule update --recursive`?

I have git repo which has nested submodules. What is the difference between below 2 commands? 

    git submodule update --init --recursive

    git submodule foreach --recursive git submodule update --init


Content Type	Original Author	Original Content on Stackoverflow
Question	user2924714	View Question on Stackoverflow
Solution 1 - Git	VonC	View Answer on Stackoverflow

git submodule update --remote vs git pull

Git Problem Overview

Git Solutions

Solution 1 - Git

Ember js - Hasmany relationships breaks after updating other tables

Failed to load Main-Class manifest attribute while running java -jar

Attributions