From: "Peter Harris" <git@peter.is-a-geek.org>
To: "Alex Riesen" <raa.lkml@gmail.com>
Cc: "Sam Vilain" <sam@vilain.net>,
"Git Mailing List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
"René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Subject: Re: [PATCH] Use find instead of perl in t5000 to get file modification time
Date: Fri, 31 Oct 2008 08:59:38 -0400 [thread overview]
Message-ID: <eaa105840810310559l29addd80i7a22c21e37231bb1@mail.gmail.com> (raw)
In-Reply-To: <20081031070003.GA4458@blimp.localdomain>
On Fri, Oct 31, 2008 at 3:00 AM, Alex Riesen wrote:
> Sam Vilain, Thu, Oct 30, 2008 06:29:14 +0100:
>> On Wed, 2008-10-29 at 11:38 +0100, Alex Riesen wrote:
>> > I could not find what exactly does the ActiveState's Perl use for its stat
>> > implementation (and honestly, have no motivation to look harder).
>> > It seems to honor TZ, but the produced time does not seem to be either
>> > local or GMT.
>>
>> See, the difference is that the perl is portable and your patch isn't.
>
> ActiveState Perl on Windows is portable? To another windows, maybe.
Quite aside from missing the point (which is that Vanilla Perl runs
everywhere, including Windows[1]), this is also factually incorrect. A
quick check of the ActiveState website would reveal ActivePerl
downloads for AIX, Linux (x86 and x86-64), Solaris (x86, SPARC, and
SPARC64), MacOSX (x86 and PPC), and source code, in addition to
Windows.
Looks pretty portable to me.
Peter Harris
[1] http://vanillaperl.com/
next prev parent reply other threads:[~2008-10-31 13:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 10:38 [PATCH] Use find instead of perl in t5000 to get file modification time Alex Riesen
2008-10-29 21:54 ` Jeff King
2008-10-30 7:26 ` Alex Riesen
2008-10-30 5:29 ` Sam Vilain
2008-10-31 7:00 ` Alex Riesen
2008-10-31 12:59 ` Peter Harris [this message]
2008-10-31 13:45 ` Alex Riesen
2008-10-31 22:14 ` Johannes Schindelin
2008-10-31 23:37 ` Alex Riesen
2008-11-01 0:23 ` Johannes Schindelin
2008-11-01 14:24 ` Alex Riesen
2008-11-01 20:37 ` Johannes Schindelin
2008-11-02 14:37 ` Alex Riesen
2008-11-02 16:05 ` Johannes Schindelin
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=eaa105840810310559l29addd80i7a22c21e37231bb1@mail.gmail.com \
--to=git@peter.is-a-geek.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.com \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=sam@vilain.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).