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

Re: [PATCH v4] submodule: add --no-fetch parameter to update command

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Jan 11, 2009, 01:32 UTC
Message-ID
<20090111103208.6117@nanako3.lavabit.com>
In-Reply-To
<1231553410-7541-2-git-send-email-git@fabian-franz.de>
Quoting Fabian Franz <git@fabian-franz.de> writes:
Show 6 quoted lines
> When -u|--use-gitmodules is given the update command uses the .gitmodules
> config file instead of the .git/config file to obtain the track parameter.
> This makes it for example possible to change branches for all submodules
> at the same time without having to sync up .git/config first.
>
> Signed-off-by: Fabian Franz <git@fabian-franz.de>
Once you start doing that, doesn't it force you to always bypass .git/config, making the current mechanism even less useful?  If you find that "having to sync up .git/config first" is inconvenient, wouldn't it be more useful for your patch if it made it easier and more convenient the procedure "to sync up .git/config first", instead of bypassing the current setup?
-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Nanako ShiraishiNext: Johannes Schindelin
Message 8 of 9 in “submodule: allow tracking of the newest revision of a branch in a submodule”
  1. submodule: allow tracking of the newest revision of a branch in a submoduleFabian Franz, Jan 10, 2009
  2. submodule: add --no-fetch parameter to update commandFabian Franz, Jan 10, 2009
  3. submodule: add --use-gitmodules parameter to update commandFabian Franz, Jan 10, 2009
  4. submodule: add +<branch> syntax for track to allow automatic pulling.Fabian Franz, Jan 10, 2009
  5. submodule: add --recursive parameter to update commandFabian Franz, Jan 10, 2009
  6. Junio C HamanoJan 11, 2009
  7. Nanako ShiraishiJan 11, 2009
  8. Nanako ShiraishiJan 11, 2009
  9. Johannes SchindelinJan 10, 2009

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.