Re: [PATCH 4/4] clone: use --progress to force progress reporting

From: Tay Ray Chuan <rctay89@gmail.com>
Date: Dec 27, 2009, 03:22 UTC
Message-ID: <be6fef0d0912261922t230047b4v395fb2f6ce3ace4d@mail.gmail.com>
In-Reply-To: <20091227012032.GE25474@genesis.frugalware.org>

Hi,

On Sun, Dec 27, 2009 at 9:20 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:

Show 26 quoted lines

> 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