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

Re: --progress option for git submodule update?

From
VLVitali Lovich <vlovich@gmail.com>
Date
Sep 11, 2015, 23:34 UTC
Message-ID
<8B026E5E-5303-45EC-984D-3F944DB6F2DB@gmail.com>
In-Reply-To
<CAGZ79kbH+917v6pmCC3w4rovEVarHp+w1tYthMwkMU2hrq=VdQ@mail.gmail.com>
& then do a git submodule init?
Show 13 quoted lines
> On Sep 11, 2015, at 4:05 PM, Stefan Beller <sbeller@google.com> wrote:
> 
> On Wed, Sep 9, 2015 at 8:06 PM, Vitali Lovich <vlovich@gmail.com> wrote:
>>> Doh! I see what you're missing now after rereading the email closely.
>>> You can add a --quiet option,
>>> but --verbose or --progress just errors out, but you want that as a
>>> possible argument for git clone
>>> inside the git submodule update code.
>> Yes exactly.
> 
> Instead of cloning with submodules, you could also clone only the
> superproject and then do a git fetch --recuse-submodules=yes -v
> instead soonish.
Previous: Stefan Beller
Message 5 of 5 in “--progress option for git submodule update?”
  1. Vitali LovichSep 9, 2015
  2. Stefan BellerSep 9, 2015
  3. Vitali LovichSep 10, 2015
  4. Stefan BellerSep 11, 2015
  5. Vitali LovichSep 11, 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.