git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Miklos Vajna" <vmiklos@frugalware.org>
Cc: "Constantine Plotnikov" <constantine.plotnikov@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] Implement git clone -v
Date: Tue, 7 Oct 2008 08:21:28 +0200	[thread overview]
Message-ID: <81b0412b0810062321h33abe076kd87b60bffdaf218b@mail.gmail.com> (raw)
In-Reply-To: <1223331590-22138-1-git-send-email-vmiklos@frugalware.org>

2008/10/7 Miklos Vajna <vmiklos@frugalware.org>:
> The new -v option forces the progressbar, even in case the output is not
> a terminal.
>
> Signed-off-by: Miklos Vajna <vmiklos@frugalware.org>
> ---
>
> On Sat, Oct 04, 2008 at 11:42:15PM +0200, Alex Riesen <raa.lkml@gmail.com> wrote:
>> 2008/10/3 Constantine Plotnikov <constantine.plotnikov@gmail.com>:
>> > Is there a way to force a progress output on stderr for git clone
>> > preferably using options or environment variables?
>>
>> No, but "-v" option is not used for anything yet, so you are free to
>> implement it.
>
> Something like this?
>

Yes. Does it work? :)

  reply	other threads:[~2008-10-07  6:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 20:01 Forcing progerss output for clone Constantine Plotnikov
2008-10-04 21:42 ` Alex Riesen
2008-10-06 22:19   ` [PATCH] Implement git clone -v Miklos Vajna
2008-10-07  6:21     ` Alex Riesen [this message]
2008-10-07 19:39       ` Miklos Vajna
2008-10-08  6:02         ` Shawn O. Pearce
2008-10-08  6:25           ` Alex Riesen
2008-10-08 23:40           ` Miklos Vajna
2008-10-09 11:06             ` Junio C Hamano
2008-10-09 15:20               ` Shawn O. Pearce
2008-10-09 21:26                 ` Miklos Vajna

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=81b0412b0810062321h33abe076kd87b60bffdaf218b@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=constantine.plotnikov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=vmiklos@frugalware.org \
    /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).