From: "Torsten Bögershausen" <tboegi@web.de>
To: vfr@lyx.org
Cc: git@vger.kernel.org, gitster@pobox.com,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH] t: Replace 'perl' by $PERL_PATH
Date: Sun, 17 Jun 2012 08:36:22 +0200 [thread overview]
Message-ID: <4FDD7AE6.6000000@web.de> (raw)
In-Reply-To: <1339441313-5296-1-git-send-email-vfr@lyx.org>
Hej,
Does this work for you?
None of the 2 patches found on pu do work here:
> a3428205e6d74542d6441baaa29d1cb1d1064d95
>Author: Vincent van Ravesteijn <vfr@lyx.org>
>Date: Mon Jun 11 19:01:53 2012 +0000
> t: Replace 'perl' by $PERL_PATH
[165c0e8f0b04b8573e91ead2890870d9e36bb39c] tests: enclose $PERL_PATH in duoble quotes
t4030 seems to be broken.
When I try to debug it, the $PERL_PATH seems to be empty:
------------------
./t4030-diff-textconv.sh --verbose | less
The ok 2 - file is considered binary by porcelain
expecting success:
git diff-tree -p HEAD^ HEAD >diff &&
:/Users/tb/projects/git/git.git/t/trash directory.t4030-diff-textconv/hexdump: line 2: -e: command not found
------------------
And the hexdump line 2 uses $PERL_PATH, which is empty:
--------------------
t/trash directory.t4030-diff-textconv> cat hexdump
#!/bin/sh
$PERL_PATH -e '$/ = undef; $_ = <>; s/./ord($&)/ge; print $_' < "$1"
tb@birne:~/projects/git/git.git/t/trash directory.t4030-diff-textconv>
-------------------
Can anybody help to find out what is going on?
next prev parent reply other threads:[~2012-06-17 6:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 19:01 [PATCH] t: Replace 'perl' by $PERL_PATH vfr
2012-06-11 19:15 ` Junio C Hamano
2012-06-12 12:34 ` Jeff King
2012-06-12 14:56 ` Junio C Hamano
2012-06-12 14:59 ` Jeff King
2012-06-12 15:36 ` Erik Faye-Lund
2012-06-12 16:08 ` Junio C Hamano
2012-06-12 16:44 ` Junio C Hamano
2012-06-12 17:05 ` Jeff King
2012-06-12 19:29 ` Vincent van Ravesteijn
2012-06-17 6:36 ` Torsten Bögershausen [this message]
2012-06-17 7:15 ` Junio C Hamano
2012-06-17 8:50 ` Torsten Bögershausen
2012-06-17 22:23 ` Junio C Hamano
2012-06-20 20:16 ` Torsten Bögershausen
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=4FDD7AE6.6000000@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vfr@lyx.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).