git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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: Sat, 11 Jan 2020 12:00:29 +0100	[thread overview]
Message-ID: <20200111120029.2baaa090@hikaru> (raw)
In-Reply-To: <xmqqblrbm7c9.fsf@gitster-ct.c.googlers.com>

On Fri, 10 Jan 2020 11:36:54 -0800
Junio C Hamano <gitster@pobox.com> wrote:

> Carlo Wood <carlo@alinoe.com> writes:
> 
> > It seems to me that the other part of the problem is printing
> > this output for submodules when nothing (needed to be) is fetched.  
> 
> Hmm, I am not sure if that is a reasonable expectation.  Would it be
> possible to tell if there is something that needs to be fetched
> without attempting to contact the other side?

That wasn't even my point though: assume that we can't know, so we
have to attempt a fetch anyway (seems indeed likely), then I'd
expect to see this message for *every* submodule, and not just
for submodules inside other submodule.

There is an asymmetry (in the output of this command) between
submodules in the top level project and submodules inside other
submodules.

This then makes me wonder after all, if the message is suppressed for
top-level submodules then can't it also be suppressed for the others
(those that are currently being printed)?

-- 
Carlo Wood <carlo@alinoe.com>

  reply	other threads:[~2020-01-11 11:00 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 [this message]
2020-01-10  9:10   ` Carlo Wood

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=20200111120029.2baaa090@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).