From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Ping Yin <pkufranky@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] git-submodule: Make update verbose for up to date path
Date: Tue, 4 Mar 2008 16:08:16 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0803041605450.22527@racer.site> (raw)
In-Reply-To: <46dff0320803040803v2f93d749t6b45fc8e47e66d21@mail.gmail.com>
Hi,
On Wed, 5 Mar 2008, Ping Yin wrote:
> When i run 'git submodule update' in a repository whose submodules are
> all clean, there is not any output which makes me not know whether this
> command are successful. I think this is not friendly.
The problem is: people ignore output. Back when merge-recursive was even
more chatty than it is now, they happily glanced over the fact that there
were _conflicts_.
So we reduced the output. Drastically.
For example, git reset --hard (amongst others) does not output a _thing_
if it succeeds. This is good. No output means it succeeded.
Now, some other commands take a while to complete, so we have a progress
which kicks in after a second or so. Still, this is just to keep the user
busy when she would otherwise think that Git hangs.
So no, I do not like submodule becoming chattier. You can add --verbose
if you want, but the default should be _quiet_.
Ciao,
Dscho
next prev parent reply other threads:[~2008-03-04 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 14:58 [PATCH] git-submodule: Make update verbose for up to date path Ping Yin
2008-03-04 15:04 ` Johannes Schindelin
2008-03-04 16:03 ` Ping Yin
2008-03-04 16:08 ` Johannes Schindelin [this message]
2008-03-04 20:31 ` Junio C Hamano
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=alpine.LSU.1.00.0803041605450.22527@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pkufranky@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox