From: Jens Lehmann <Jens.Lehmann@web.de>
To: Chris Kees <cekees@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: --progress for git submodule update?
Date: Sun, 11 Mar 2012 21:50:05 +0100 [thread overview]
Message-ID: <4F5D0FFD.1020509@web.de> (raw)
In-Reply-To: <CAOVFbFiBOH2MyC3HUtf=hA_PssSRENW7uwpBVxh0TwnO7h90XA@mail.gmail.com>
Am 10.03.2012 08:17, schrieb Chris Kees:
> 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?
next prev parent reply other threads:[~2012-03-11 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 7:17 --progress for git submodule update? Chris Kees
2012-03-11 20:50 ` Jens Lehmann [this message]
2012-03-13 2:17 ` Chris Kees
2012-03-14 19:42 ` Jens Lehmann
2012-03-14 21:45 ` Junio C Hamano
2012-03-15 3:43 ` Chris Kees
2012-03-15 22:34 ` Jens Lehmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5D0FFD.1020509@web.de \
--to=jens.lehmann@web.de \
--cc=cekees@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).