From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Jeff King <peff@peff.net>, Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: t9700-perl-git.sh is broken on some configurations
Date: Fri, 04 Mar 2016 11:58:24 +0100 [thread overview]
Message-ID: <1457089104.2660.79.camel@kaarsemaker.net> (raw)
In-Reply-To: <20160304085649.GA29752@sigill.intra.peff.net>
On vr, 2016-03-04 at 03:56 -0500, Jeff King wrote:
> ? Those are just guesses, but if we are tickling a bug in perl's parser,
> this might avoid them. I also wondered when "/r" appeared. It was in
> 5.14, so you're presumably good there. The "use" statement at the top of
> the script says "5.008", so perhaps we should be writing it out longhand
> anyway (that version is "only" 5 years old, so I suspect there are still
> systems around with 5.12 or older).
Knowing the system Christian is testing on, I think the problem is that
the tests are actually being run against perl 5.10, which RHEL 6 ships
as system perl. As that's still a supported OS, writing tests in a form
compatible with it would be a good thing :)
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
next prev parent reply other threads:[~2016-03-04 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 8:13 t9700-perl-git.sh is broken on some configurations Christian Couder
2016-03-04 8:56 ` Jeff King
2016-03-04 10:30 ` Christian Couder
2016-03-04 11:45 ` Jeff King
2016-03-04 10:58 ` Dennis Kaarsemaker [this message]
2016-03-04 11:43 ` [PATCH] t9700: fix test for perl older than 5.14 Jeff King
2016-03-04 12:21 ` Dennis Kaarsemaker
2016-03-04 20:12 ` Christian Couder
2016-03-04 16:21 ` Johannes Schindelin
2016-03-04 18:15 ` 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=1457089104.2660.79.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.