git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nicolas Pitre <nico@fluxnic.net>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
	Neal Kreitzinger <neal@rsss.com>
Subject: Re: [PATCH RFC/RFD] clone: quell the progress report from init
Date: Tue, 30 Mar 2010 10:43:03 +0200	[thread overview]
Message-ID: <81b0412b1003300143s55a93fcqf9a6d5d727a4e786@mail.gmail.com> (raw)
In-Reply-To: <7v7houxu8n.fsf@alter.siamese.dyndns.org>

On Tue, Mar 30, 2010 at 07:18, Junio C Hamano <gitster@pobox.com> wrote:
> Nicolas Pitre <nico@fluxnic.net> writes:
>
>> Personally I like your suggestion above.  A clone is not something you
>> perform repeatedly, and it is the first thing that random people told to

Well, I have git clone in my top-20 used commands. I'm reasonably sure
it is used many times in a row too.

>> use Git to grab a piece of code will do.  Better give them some comfort
>> by telling them what is happening.
>
> Here is what such a change may look like.  I'll leave adjusting
> documentation (namely, tutorials) and perhaps tests as an exercise to the
> readers ;-)

There still is no way to make things quiet by default.

And at least for me the annoyance was when using it in command line,
interactively. So yes, it makes it possible to make clone quieter, but I
wont use it, because I have to either make an alias for git (and that
on every system I might come upon), or type in "-q" every time, at which
case I can also live with a little more output.

But even if it is of no immediate use to me personall, I still like the patch:
now I can make some scripts quieter (with less risk of removing something
interesting by piping everything to /dev/null).

  parent reply	other threads:[~2010-03-30  8:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 22:44 color (red) for error messages on all git commands Neal Kreitzinger
2010-03-24 22:58 ` Sverre Rabbelier
2010-03-24 23:12   ` Alex Riesen
2010-03-25  8:43     ` Michael J Gruber
2010-03-25  8:46       ` [PATCH RFC/RFD] clone: quell the progress report from init Michael J Gruber
2010-03-25  9:02         ` Alex Riesen
2010-03-25  9:26           ` Michael J Gruber
2010-03-25 16:31         ` Tilo Schwarz
2010-03-26 19:32         ` Junio C Hamano
2010-03-26 20:16           ` Nicolas Pitre
2010-03-26 20:24             ` Junio C Hamano
2010-03-30  5:18             ` Junio C Hamano
2010-03-30  8:05               ` Michael J Gruber
2010-03-30  8:43               ` Alex Riesen [this message]
2010-04-01 22:03               ` [PATCH] clone: quell the progress report from init and report on clone Michael J Gruber
2010-04-02  7:28                 ` Junio C Hamano
2010-04-04 13:02                   ` Michael J Gruber
2010-04-23 12:37                     ` Michael J Gruber

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=81b0412b1003300143s55a93fcqf9a6d5d727a4e786@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=neal@rsss.com \
    --cc=nico@fluxnic.net \
    --cc=srabbelier@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;
as well as URLs for NNTP newsgroup(s).