From: Carlo Wood <carlo@alinoe.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git submodule update strange output behavior.
Date: Fri, 10 Jan 2020 10:10:40 +0100 [thread overview]
Message-ID: <20200110101040.00b93fa7@hikaru> (raw)
In-Reply-To: <xmqqtv54zcik.fsf@gitster-ct.c.googlers.com>
That seems only part of the problem, but yes.
It is only part of the problem because without --quiet
I get the same output; that is - the top-level is still
quiet, but the submodules aren't. That is out of balance
imho.
On Thu, 09 Jan 2020 10:54:27 -0800
Junio C Hamano <gitster@pobox.com> wrote:
> Carlo Wood <carlo@alinoe.com> writes:
>
> > In a project containing submodules, one of the submodules
> > contains a submodule itself, which in turn also contains
> > a submodule.
> >
> > Overview:
> >
> > project/foobar [submodule]
> > project/cwm4 [submodule]
> > project/evio [submodule]
> > project/evio/protocol/matrixssl [submodule]
> > project/evio/protocol/matrixssl/cwm4 [submodule]
> >
> > ('protocol' is a normal subdirectory)
> >
> > Running (with or without the --quiet),
> >
> > $ git submodule --quiet update --init --recursive --remote
> > Fetching submodule protocol/matrixssl
> > Fetching submodule protocol/matrixssl/cwm4
> > Fetching submodule cwm4
> >
> > This is odd (a bug imho) because
> >
> > 1) it seems to only print this fetching information for submodules
> > inside submodules, not for the top-level submodules.
> > 2) it even prints this when using --quiet
> > 3) it prints this every time (also when there is nothing more to
> > fetch).
>
>
> Sounds like a symptom of (a) the top-level "git submodule update"
> knowing how to react to "--quiet" but (b) it forgets to pass down
> the "--quiet" when it recursively runs "git submodule update" in its
> submodules?
>
--
Carlo Wood <carlo@alinoe.com>
prev parent reply other threads:[~2020-01-10 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 18:20 git submodule update strange output behavior Carlo Wood
2020-01-09 18:54 ` Junio C Hamano
2020-01-09 20:03 ` Junio C Hamano
2020-01-10 9:12 ` Carlo Wood
2020-01-10 19:36 ` Junio C Hamano
2020-01-11 11:00 ` Carlo Wood
2020-01-10 9:10 ` Carlo Wood [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200110101040.00b93fa7@hikaru \
--to=carlo@alinoe.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).