Re: [PATCH] Silence cpio's "N blocks" output when cloning locally
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 31, 2008, 00:19 UTC
- Message-ID
- <7v1w5rwxs7.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.LSU.1.00.0803281728530.18259@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 19 quoted lines
> On Fri, 28 Mar 2008, Wincent Colaiuta wrote: > >> El 28/3/2008, a las 14:01, Johannes Schindelin escribió: >> >> >On Fri, 28 Mar 2008, Bryan Donlan wrote: >> > >> > >Pass --quiet to cpio in git-clone to hide the (confusing) "0 blocks" >> > >message. For compatibility with operating systems which might not >> > >support GNUisms, the presence of --quiet is probed for by grepping >> > >cpio's --help output. >> > >> >We have a builtin clone which is almost ready for 'next', and I think >> >that this issue would be resolved there anyway. >> >> In any case, I'd rather see the cpio check at configure-time rather than >> run-time. > > That would have to be done via ./configure, missing out those people who > do not run ./configure, but just make.
Runtime is just fine for this case. Unlike other commands, clone is not something you run all the time. Anything more elaborate is just overengineered.