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

Re: submodule update --force

From
Junio C Hamano <gitster@pobox.com>
Date
May 10, 2012, 14:58 UTC
Message-ID
<7v8vh0ozge.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAHOQ7J_6+sfU6egjvVSPj-FAS6zjSUT=a057=kz_wYbogHLMMA@mail.gmail.com>
Stefan Zager <szager@google.com> writes:
Show 5 quoted lines
> ...  To my mind, any
> `git submodule` command should *always* run on the first level of
> submodules.  If you're going to specify --no-recurse, then why are you
> running `git submodule` at all?  I think 'recursion' only applies to
> moving beyond the first level of submodules.
Very true.
Submodule folks, any opinion on the Stefan's approach?
Previous: Stefan ZagerNext: Heiko Voigt
Message 5 of 12 in “submodule update --force”
  1. Stefan ZagerMay 9, 2012
  2. Junio C HamanoMay 10, 2012
  3. Junio C HamanoMay 10, 2012
  4. Stefan ZagerMay 10, 2012
  5. Junio C HamanoMay 10, 2012
  6. Heiko VoigtMay 10, 2012
  7. Phil HordMay 11, 2012
  8. Heiko VoigtMay 14, 2012
  9. Stefan ZagerMay 14, 2012
  10. Heiko VoigtMay 14, 2012
  11. Stefan ZagerMay 14, 2012
  12. Heiko VoigtMay 14, 2012

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.