From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Wincent Colaiuta <win@wincent.com>,
Bryan Donlan <bdonlan@fushizen.net>,
git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Silence cpio's "N blocks" output when cloning locally
Date: Sun, 30 Mar 2008 17:19:04 -0700 [thread overview]
Message-ID: <7v1w5rwxs7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: alpine.LSU.1.00.0803281728530.18259@racer.site
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 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.
prev parent reply other threads:[~2008-03-31 0:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 6:19 [PATCH] Silence cpio's "N blocks" output when cloning locally Bryan Donlan
2008-03-28 13:01 ` Johannes Schindelin
2008-03-28 16:12 ` Wincent Colaiuta
2008-03-28 16:29 ` Johannes Schindelin
2008-03-28 18:59 ` Bryan Donlan
2008-03-31 0:19 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v1w5rwxs7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bdonlan@fushizen.net \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).