threads / discuss / 42525

RFC: have a config option for running submodule update after checkout <revision>

Subject: RFC: have a config option for running submodule update after checkout <revision>

## tl;dr

2 messages between Jun 3, 2016 and Jun 3, 2016.

replies: 1people: 1as markdown or json

Stefan Beller· Jun 3, 2016, 22:53 UTC · lore

When checking out a new revision in a repo with submodules, one of the first commands after checkout is `git submodule update` to make sure the submodules are updated.

I propose to have a switch which when turned on automatically runs `git submodule update` for you instead of implementing proper submodule support in checkout for example.

advantages:
* users are already used to the quirks of `submodule update`
* a lot of config options exist for the behavior of `submodule update`

disadvantages:
* it's not `done right`, i.e. dealing with gitlinks in read-tree/unpack-tree
   but just another command chained after checkout, so we would do that
   for pull too eventually?

What do you think?

Thanks, Stefan

Stefan Beller· Jun 3, 2016, 23:30 UTC · re: Stefan Beller · lore

Re: RFC: have a config option for running submodule update after checkout <revision>

On Fri, Jun 3, 2016 at 3:53 PM, Stefan Beller <sbeller@google.com> wrote:

> disadvantages:
> * it's not `done right`, i.e. dealing with gitlinks in read-tree/unpack-tree
>    but just another command chained after checkout, so we would do that
>    for pull too eventually?

Well one argument against the disadvantage is that we have `pull` already, which is essentially fetch and merge as a chain of commands and nobody bothers about having a chain of commands.

Show 5 quoted lines

>
> What do you think?
>
> Thanks,
> Stefan