git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org, Nicolas Pitre <nico@fluxnic.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 4/4] clone: use --progress to force progress reporting
Date: Sun, 27 Dec 2009 11:22:22 +0800	[thread overview]
Message-ID: <be6fef0d0912261922t230047b4v395fb2f6ce3ace4d@mail.gmail.com> (raw)
In-Reply-To: <20091227012032.GE25474@genesis.frugalware.org>

Hi,

On Sun, Dec 27, 2009 at 9:20 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Sat, Dec 26, 2009 at 01:12:06AM +0800, Tay Ray Chuan <rctay89@gmail.com> wrote:
>> -v/--verbose now does not force progress reporting. Make git-clone.txt
>> say so.
>>
>> This should cover all the bases in 21188b1 (Implement git clone -v),
>> which implemented the option to force progress reporting.
>>
>> Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
>> ---
>>  Documentation/git-clone.txt |    3 +++
>>  builtin-clone.c             |    8 ++++++--
>>  t/t5702-clone-options.sh    |    3 ++-
>>  3 files changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt
>> index e722e6c..f43c8b2 100644
>> --- a/Documentation/git-clone.txt
>> +++ b/Documentation/git-clone.txt
>> @@ -102,6 +102,9 @@ objects from the source repository into a pack in the cloned repository.
>>
>>  --verbose::
>>  -v::
>> +     Run verbosely.
>
> What about mentioning this "does not force progress reporting" behaviour
> in documentation of the "new" -v option?

Ok.

-- 
Cheers,
Ray Chuan

  reply	other threads:[~2009-12-27  3:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09  4:54 [PATCH/RFC] Add progress options Brent Goodrick
2009-12-25 17:12 ` [PATCH 0/4] clone: use --progress to mean -v Tay Ray Chuan
2009-12-25 17:12   ` [PATCH 1/4] check stderr with isatty() instead of stdout when deciding to show progress Tay Ray Chuan
2009-12-25 17:12     ` [PATCH 2/4] git-clone.txt: reword description of progress behaviour Tay Ray Chuan
2009-12-25 17:12       ` [PATCH 3/4] clone: set transport->verbose when -v/--verbose is used Tay Ray Chuan
2009-12-25 17:12         ` [PATCH 4/4] clone: use --progress to force progress reporting Tay Ray Chuan
2009-12-27  1:20           ` Miklos Vajna
2009-12-27  3:22             ` Tay Ray Chuan [this message]
2009-12-26  8:53   ` [PATCH 0/4] clone: use --progress to mean -v Johannes Schindelin
2009-12-27  3:27     ` Tay Ray Chuan
2009-12-29  1:30       ` Junio C Hamano
2009-12-29  3:06         ` Tay Ray Chuan

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=be6fef0d0912261922t230047b4v395fb2f6ce3ace4d@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nico@fluxnic.net \
    --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).