From: Jeff King <peff@peff.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Add test-tr: poor-man tr
Date: Thu, 12 Jun 2008 02:23:09 -0400 [thread overview]
Message-ID: <20080612062309.GA31816@sigill.intra.peff.net> (raw)
In-Reply-To: <20080612060152.GA3798@steel.home>
On Thu, Jun 12, 2008 at 08:01:52AM +0200, Alex Riesen wrote:
> Frankly, it started because I wanted to minimize use of Perl on
> Windows (because I can't get around ActiveState Perl at work, and it
> breaks almost everything it touches). Accidentally, it is also faster
> there (maybe just because it's smaller).
Ah, right. Well, I am not opposed to getting rid of perl in the test
scripts (there is core functionality provided by perl, so one can easily
run git on a system with no perl at all).
However, even with your patch, there is still some perl left, so I am
not sure that it has really bought us very much.
> But, as was already noted, tr does not behave the same for all
> platforms (there were even differences in output, BSD or Solaris put
> out a stray LF?).
I think those were all resolved by using perl, and your patch replaces
them with test-tr.
> > Or is your rationale "this will prevent people from screwing up the test
> > scripts accidentally in the future"?
> We just can't have that. Nothing can prevent people from screwing up
> anything in any given point of time :)
Heh. At least we can yell at them after the fact for not using the
available tool. :)
> In any case, I wont push this change too hard. I must admit, that
> there is no real good reason besides one "screwed" company using
> obsoleted tools in a weird way. And it is a maintenance effort (and
> people will forget to use test-tr instead of perl and tr).
There is maintenance effort either way; people need to know not to do
unportable things with tr (and other tools), and the solution to that is
to run the test scripts on each platform (something we are starting to
do).
So I am not opposed to test-tr, I just wanted you to explain it better
in the commit log. ;)
-Peff
next prev parent reply other threads:[~2008-06-12 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 18:25 [PATCH] Add test-tr: poor-man tr Alex Riesen, Alex Riesen
2008-06-11 18:26 ` [PATCH] Use test-tr in the tests Alex Riesen
2008-06-11 21:34 ` [PATCH] Add test-tr: poor-man tr Alex Riesen
2008-06-11 22:54 ` Jeff King
2008-06-12 6:01 ` Alex Riesen
2008-06-12 6:23 ` Jeff King [this message]
2008-06-12 6:28 ` Jeff King
2008-06-12 20:32 ` Alex Riesen
2008-06-13 6:02 ` Jeff King
2008-06-13 17:26 ` Alex Riesen
2008-06-13 18:00 ` Jeff King
2008-06-12 6:32 ` Alf Clement
2008-06-12 7:25 ` Johannes Schindelin
2008-06-12 20:20 ` Alex Riesen, Alex Riesen
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=20080612062309.GA31816@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@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).