From: Junio C Hamano <gitster@pobox.com>
To: Nick Andrew <nick@nick-andrew.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Enable git rev-list to parse --quiet
Date: Sun, 20 Jul 2008 00:56:28 -0700 [thread overview]
Message-ID: <7vwsjhc7kj.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080718092001.GD16102@mail.local.tull.net> (Nick Andrew's message of "Fri, 18 Jul 2008 19:20:01 +1000")
Nick Andrew <nick@nick-andrew.net> writes:
> ...Without
> a working "--quiet" nor exit code I can pipe the output to "wc -l"
> but is there a more efficient/reliable way to implement the requirement?
Did you read the whole thread before asking the above question?
IOW, does this answer the above question?
http://mid.gmane.org/7vy73zd8ok.fsf@gitster.siamese.dyndns.org
next prev parent reply other threads:[~2008-07-20 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 4:05 [PATCH] Enable git rev-list to parse --quiet Nick Andrew
2008-07-18 5:42 ` Junio C Hamano
2008-07-18 6:10 ` Junio C Hamano
2008-07-18 9:20 ` Nick Andrew
2008-07-18 10:50 ` Johannes Schindelin
2008-07-20 7:56 ` Junio C Hamano [this message]
2008-07-20 12:04 ` Nick Andrew
2008-07-20 18:31 ` Junio C Hamano
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=7vwsjhc7kj.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=nick@nick-andrew.net \
/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).