git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Stefan Beller <sbeller@google.com>
Date
Jun 3, 2016, 23:30 UTC
Message-ID
<CAGZ79kYC9Pub1RhcedLBqxK+pBunmN1DwjmWf83MUbY9pdvwhQ@mail.gmail.com>
In-Reply-To
<CAGZ79kb9xHNYysb6gS9nPWvFW3cgcW-ey+5qyfTHTPGkT0fNfw@mail.gmail.com>
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
Previous: Stefan Beller
Message 2 of 2 in “RFC: have a config option for running submodule update after checkout <revision>”
  1. Stefan BellerJun 3, 2016
  2. Stefan BellerJun 3, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.