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

Re: --progress for git submodule update?

From
Jens Lehmann <jens.lehmann@web.de>
Date
Mar 11, 2012, 20:50 UTC
Message-ID
<4F5D0FFD.1020509@web.de>
In-Reply-To
<CAOVFbFiBOH2MyC3HUtf=hA_PssSRENW7uwpBVxh0TwnO7h90XA@mail.gmail.com>
Am 10.03.2012 08:17, schrieb Chris Kees:
Show 5 quoted lines
> Would it be reasonable to have a --progress option for 'git submodule
> update'? I'm using buildbot with a git repository containing large
> submodules, and buildbot times out on the submodule update
> occasionally because there is no output for long periods of time.
> Adjusting buildbot's timeout factor will do for me in the short run.

As cloning a submodule talks a lot about its progress am I right suspecting it is the checkout part that is taking so long for you? The submodule script always uses the -q option for git checkout (which also gets rid of the unwanted "detached HEAD" messages). So AFAICS before a --progress option could be added to the submodule script, git checkout would have to learn an option to show progress but not the detached HEAD message (or to just suppress that advice).

What times are we talking about here?
Previous: Chris KeesNext: Chris Kees
Message 2 of 7 in “--progress for git submodule update?”
  1. Chris KeesMar 10, 2012
  2. Jens LehmannMar 11, 2012
  3. Chris KeesMar 13, 2012
  4. Jens LehmannMar 14, 2012
  5. Junio C HamanoMar 14, 2012
  6. Chris KeesMar 15, 2012
  7. Jens LehmannMar 15, 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.