From: Jens Lehmann <Jens.Lehmann@web.de>
To: Orgad and Raizel Shaneh <orgads@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-submodule: respect -q for add/update
Date: Wed, 05 Sep 2012 22:33:39 +0200 [thread overview]
Message-ID: <5047B723.4050201@web.de> (raw)
In-Reply-To: <CAGHpTBJ6hWJKaQvN4oByrest_FB1fGDKa=ge4fM1HWmSWZ1tkw@mail.gmail.com>
Am 05.09.2012 13:42, schrieb Orgad and Raizel Shaneh:
> On Tue, Sep 4, 2012 at 6:28 PM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
>>
>> Am 04.09.2012 09:31, schrieb Orgad Shaneh:
>>> Signed-off-by: Orgad Shaneh <orgads@gmail.com>
>>
>> Before the "Signed-off-by" is the place where you should have
>> explained why this would be a worthwhile change ;-)
>>
>> To me this looks like you make the default noisier and require an
>> explicit "-q" to make it quiet again. There is a reason you don't
>> normally get bothered with the output of the checkout command run
>> under the hood of git submodule add/update, so I don't think this
>> change makes things better.
>>
>> But you might want to think about adding a "-v/--verbose" flag to
>> make the submodule add/update checkouts more verbose, in case you
>> care about the output of the checkout command. That would be a
>> sane thing to do, so what about changing your patch into this
>> direction?
>>
>
> I don't agree the default should be quiet. That's what the (submodule)
> -q flag is there for.
Nope, the -q flag is to silence *all* output except errors. And it
makes perfect sense for high level commands to hide the output of
the commands run under the hood like we do here.
> When I run 'git submodule update' I don't expect to be in the dark
> until the submodule/s finishes checkout, this sometimes can take a
> significant amount of time and feedback is expected.
As I said, add a verbose flag so you can see in detail what is going
on.
prev parent reply other threads:[~2012-09-05 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 7:31 [PATCH] git-submodule: respect -q for add/update Orgad Shaneh
2012-09-04 15:28 ` Jens Lehmann
2012-09-05 11:42 ` Orgad and Raizel Shaneh
2012-09-05 20:33 ` Jens Lehmann [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5047B723.4050201@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=orgads@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.