[PATCH modular 2/2] Force progress on 'git clone'.

Jeremy Huddleston jeremyhu at freedesktop.org
Tue Oct 5 12:59:26 PDT 2010


You could do something like this to test the version (I forget portability rules with POSIX shells, so if the variable magic is a bash-ism, you'll want to use sed instead:

V=$(git version | cut -f3 -d' ')
VMA=${V%%.*}
VNMA=${V#*.}
VMI=${VNMA%%.*}

[ ${VMA} -gt 1 -o ( ${VMA} -eq 1 -a ${VMI} -ge 7 ) ]


On Oct 5, 2010, at 11:54, Gaetan Nadon wrote:

> On Tue, 2010-10-05 at 10:32 -0400, Trevor Woerner wrote:
> 
>> From: Trevor Woerner <twoerner at gmail.com>
>> 
>> If its output is redirected, git clone will not show its progress.
>> This
>> modification does not introduce any change when the output is not
>> redirected.
>> 
>> Signed-off-by: Trevor Woerner <twoerner at gmail.com>
>> 
> 
> 
> Unfortunately the --progress is only available on the very recent
> version of git 1.7.
> 
> One can do a feature test like Autoconf does, but I am not sure it is
> worth the effort.
> 
> _______________________________________________
> xorg-devel at lists.x.org: X.Org development
> Archives: http://lists.x.org/archives/xorg-devel
> Info: http://lists.x.org/mailman/listinfo/xorg-devel



More information about the xorg-devel mailing list