From: Junio C Hamano <gitster@pobox.com>
To: Dan Loewenherz <daniel.loewenherz@yale.edu>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] Eliminate redirection to stdout and stderr when quiet option is available
Date: Thu, 14 May 2009 00:27:20 -0700 [thread overview]
Message-ID: <7vzldgw3dz.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <6f5a4e780905140013g75d85558tfaa3c85430f8a8a3@mail.gmail.com> (Dan Loewenherz's message of "Thu\, 14 May 2009 03\:13\:02 -0400")
Dan Loewenherz <daniel.loewenherz@yale.edu> writes:
> diff --git a/git-add--interactive.perl b/git-add--interactive.perl
> index f6e536e..e1106c9 100755
> --- a/git-add--interactive.perl
> +++ b/git-add--interactive.perl
> @@ -158,7 +158,7 @@ my $status_head = sprintf($status_fmt, 'staged',
> 'unstaged', 'path');
> {
> my $initial;
> sub is_initial_commit {
> - $initial = system('git rev-parse HEAD -- >/dev/null 2>&1') != 0
> + $initial = system('git rev-parse -q HEAD -- ') != 0
Isn't this conversion wrong?
$ git rev-parse -q HEAD --
95405ba6cf7adeaa4a066e8a3a1b76b73f7b9341
> diff --git a/git-am.sh b/git-am.sh
> index 6d1848b..8a86d05 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -36,7 +36,7 @@ cd_to_toplevel
> git var GIT_COMMITTER_IDENT >/dev/null ||
> die "You need to set your committer info first"
>
> -if git rev-parse --verify -q HEAD >/dev/null
> +if git rev-parse --verify -q HEAD
Likewise.
Should I spend more time myself, or will you double check the patch and
resubmit?
next prev parent reply other threads:[~2009-05-14 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 7:13 [PATCH] Eliminate redirection to stdout and stderr when quiet option is available Dan Loewenherz
2009-05-14 7:27 ` Junio C Hamano [this message]
2009-05-14 7:35 ` Johannes Schindelin
2009-05-14 7:48 ` Dan Loewenherz
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=7vzldgw3dz.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=daniel.loewenherz@yale.edu \
--cc=git@vger.kernel.org \
/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).