From: Junio C Hamano <junkio@cox.net>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Michal Rokos <michal.rokos@nextsoft.cz>,
git@vger.kernel.org
Subject: Re: [Patch] Using 'perl' in *.sh
Date: Sun, 09 Jul 2006 03:14:39 -0700 [thread overview]
Message-ID: <7vd5cfnkz4.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060709095114.GQ22573@lug-owl.de> (Jan-Benedict Glaw's message of "Sun, 9 Jul 2006 11:51:15 +0200")
Jan-Benedict Glaw <jbglaw@lug-owl.de> writes:
> My personal oppinion is to call perl scripts as `perl foo.pl' and thus
> let the user decide (by means of setting $PATH) which perl incarnation
> she wants to use.
Sounds sane, and I was wrong.
We should be able to do that for perl (we cannot in general do
that for GNU tools since some people seem to like renaming them
from foo to gfoo).
Michal, is there a reason you do not want to have the version of
perl you teach git tools via #! lines with PERL_PATH on your $PATH?
next prev parent reply other threads:[~2006-07-09 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 15:32 [Patch] Using 'perl' in *.sh Michal Rokos
2006-07-08 18:27 ` Junio C Hamano
2006-07-09 9:46 ` Alex Riesen
2006-07-09 9:51 ` Jan-Benedict Glaw
2006-07-09 10:14 ` Junio C Hamano [this message]
2006-07-09 12:41 ` Michal Rokos
2006-07-09 14:02 ` Randal L. Schwartz
2006-07-09 16:24 ` Jan-Benedict Glaw
2006-07-09 20:33 ` Junio C Hamano
2006-07-09 21:20 ` Jan-Benedict Glaw
2006-07-10 5:41 ` Michal Rokos
2006-07-10 13:09 ` Randal L. Schwartz
2006-07-10 13:16 ` Johannes Schindelin
2006-07-10 13:29 ` Randal L. Schwartz
2006-07-09 10:09 ` Yakov Lerner
2006-07-09 12:17 ` 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=7vd5cfnkz4.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jbglaw@lug-owl.de \
--cc=michal.rokos@nextsoft.cz \
--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 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.