[Enhancement] Updating Submodules Improvements

[Doodeletion]

Updating specific submodule

To update a specific submodule you currently have to click Update Submodule, then un-tick All submodules and finally choose the submodule you want to update from the dropdown.

It would be nice if you could update a specific submodule directly.
I can think of 2 ways to do this:

• add an update option to submodule context menu
• add inline update button to submodule (like the button in the submodules header for updating all submodules)

---

Updating with --remote

To use update --remote you currently have to use the normal update submodules button and then tick Use --remote option.
This is very accurate to Git's behavior, but I think it would be better to have 2 separate buttons for git submodule update and git submodule update --remote:

• git submodule update reads what submodule commit the superproject expects and then sets the submodule to that expected state (fetching if the referenced commit is not available locally) Git Doc
• git submodule update --remote changes what submodule commit the superproject expects to the newest commit on the submodule's remote-tracking branch Git Doc

So the 2 commands do something very different: one makes sure that your submodule is in the expected state, while the other changes what state is expected.

[love-linger]

Updating specific submodule

This is already done by commit 937ad0c.

[Doodeletion]

Oh wow you've gotten so quick with implementing issues you're done before I even open them :)

[goran-w]

@Doodeletion, @love-linger - to fully support the submodule update --remote feature, we should also add UI support for the branch info on submodules :

• Viewing it (in tooltip)
  • (Stored in git-config submodule.<submod_name>.branch)
• Setting it (during Add Submodule)
  • git submodule add -b <branch> ...
• Editing/clearing it (by new command Set Branch)
  • git submodule set-branch --branch <new_branch> <submod_path> (set)
  • git submodule set-branch --default <submod_path> (clear)

(And possibly also for git-config branch.<submod_name>.remote, but that's maybe more seldom modified, defaults to origin, also there's not special command git submodule set-remote like the ones for set-branch and set-url...)

[love-linger]

git submodule update --remote does not depends on git submodule set-branch command, since there's always a ref named HEAD in remote branch.

[love-linger]

Done

[goran-w]

Great, thanks!

git submodule update --remote does not depends on git submodule set-branch command, since there's always a ref named HEAD in remote branch.

It's at least affected (overridden) by it, according to the documentation for git submodule --remote :

"The remote branch used defaults to the remote HEAD, but the branch name may be overridden by setting the submodule.<name>.branch option"

(The mentioned option is the same config-value that's changed by git submodule set-branch.)