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

Re: git submodule: update=!command

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2015, 20:49 UTC
Message-ID
<xmqqy4mvmjs9.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1426620537.1785877.241673949.72FB3B40@webmail.messagingengine.com>
Ryan Lortie <desrt@desrt.ca> writes:
Show 7 quoted lines
> 'man git-submodule' contains mention (in one place) that:
>
>     Setting the key submodule.$name.update to !command
>     will cause command to be run.
>
> This is not documented in 'man gitmodules' (which documents the other
> possible values for the 'update' key)

Yes, that is deliberate, because you cannot use !command in .gitmodules that is tracked for security reasons.

With more recent versions of Git, namely, the versions after 30a52c1d (Merge branch 'ms/submodule-update-config-doc' into maint, 2015-03-13), the documentation pages already have updated descriptions around this area.

Previous: Chris PackhamNext: Ryan Lortie
Message 5 of 10 in “git submodule: update=!command”
  1. Ryan LortieMar 17, 2015
  2. Jeff KingMar 17, 2015
  3. Ryan LortieMar 17, 2015
  4. Chris PackhamMar 18, 2015
  5. Junio C HamanoMar 17, 2015
  6. Ryan LortieMar 17, 2015
  7. Junio C HamanoMar 17, 2015
  8. Ryan LortieMar 17, 2015
  9. Chris PackhamMar 18, 2015
  10. Chris PackhamMar 18, 2015

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.