Re: [PATCH 4/4] clone: use --progress to force progress reporting
- From
Miklos Vajna <vmiklos@frugalware.org>
- Date
- Dec 27, 2009, 01:20 UTC
- Message-ID
- <20091227012032.GE25474@genesis.frugalware.org>
- In-Reply-To
- <1261761126-5784-5-git-send-email-rctay89@gmail.com>
On Sat, Dec 26, 2009 at 01:12:06AM +0800, Tay Ray Chuan <rctay89@gmail.com> wrote:
Show 22 quoted lines
> -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?