From 5a518ad4679c91f0d0afd38fcc3cbf04e8699c46 Mon Sep 17 00:00:00 2001 From: Tay Ray Chuan Date: Sat, 26 Dec 2009 01:12:06 +0800 Subject: clone: use --progress to force progress reporting Follow the argument convention of git-pack-objects, such that a separate option (--preogress) is used to force progress reporting instead of -v/--verbose. -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 Signed-off-by: Junio C Hamano --- Documentation/git-clone.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'Documentation/git-clone.txt') diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index e722e6cfd2..f43c8b2c08 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. + +--progress:: Progress status is reported on the standard error stream by default when it is attached to a terminal, unless -q is specified. This flag forces progress status even if the -- cgit v1.2.3