From: Jonathan Nieder <jrnieder@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Sverre Rabbelier <srabbelier@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/2] revert: refactor code that prints success or failure message
Date: Tue, 13 Jul 2010 17:16:20 -0500 [thread overview]
Message-ID: <20100713221620.GA4763@burratino> (raw)
In-Reply-To: <201007132302.59324.chriscool@tuxfamily.org>
Christian Couder wrote:
> I don't know about sh -x but there is this code in test-lib.sh to warn about
> GIT_TRACE use:
>
> case $(echo $GIT_TRACE |tr "[A-Z]" "[a-z]") in
> 1|2|true)
> echo "* warning: Some tests will not work if GIT_TRACE" \
> "is set as to trace on STDERR ! *"
> echo "* warning: Please set GIT_TRACE to something" \
> "other than 1, 2 or true ! *"
> ;;
> esac
Oh! I just remembered
http://thread.gmane.org/gmane.comp.version-control.git/146767
I guess the answer is we half-support it. Maybe a test_cmp_err()
helper to strip out xtrace[1] and GIT_TRACE[2] output is needed.
>> Summary: I was misled by the commit message.
[...]
> Ok, I will improve it.
Thanks, and sorry for the unfocused review.
Jonathan
[1] Sadly, it is not obvious to me that the format of output produced
by set -x is portable. Any sufficiently unixy system (e.g., any
system supporting the Posix User Portability Utilities option) will
use $PS4 which defaults to ‘+ ’ at the beginning of trace lines, but
even for Posix that is only optional.
[2] All trace output starts with ‘trace: ’, with one exception.
diff --git a/exec_cmd.c b/exec_cmd.c
index bf22570..75d2930 100644
--- a/exec_cmd.c
+++ b/exec_cmd.c
@@ -28,7 +28,7 @@ const char *system_path(const char *path)
!(prefix = strip_path_suffix(argv0_path, BINDIR)) &&
!(prefix = strip_path_suffix(argv0_path, "git"))) {
prefix = PREFIX;
- trace_printf("RUNTIME_PREFIX requested, "
+ trace_printf("trace: RUNTIME_PREFIX requested, "
"but prefix computation failed. "
"Using static fallback '%s'.\n", prefix);
}
--
next prev parent reply other threads:[~2010-07-13 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 11:54 [PATCH 1/2] revert: refactor code that prints success or failure message Christian Couder
2010-07-12 16:30 ` Jonathan Nieder
2010-07-13 21:02 ` Christian Couder
2010-07-13 22:16 ` Jonathan Nieder [this message]
2010-07-15 9:26 ` Christian Couder
2010-07-12 18:27 ` Ramkumar Ramachandra
2010-07-13 21:16 ` Christian Couder
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=20100713221620.GA4763@burratino \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.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).