From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pat Pannuto <pat.pannuto@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Johannes Sixt <j6t@kdbg.org>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] Use 'env' to find perl instead of fixed path
Date: Fri, 13 Jan 2017 16:21:39 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1701131621170.3469@virtualbox> (raw)
In-Reply-To: <CAAnLKaGvz4Wzs36gMSdoYCg+tzx6KFCe59FNnk5zNQ-L58ww1g@mail.gmail.com>
Hi Pat,
On Thu, 12 Jan 2017, Pat Pannuto wrote:
> You may still want the 1/2 patch in this series, just to make things
> internally consistent with "-w" vs "use warnings;" inside git's perl
> scripts.
Yes, I like that patch.
Ciao,
Johannes
next prev parent reply other threads:[~2017-01-13 15:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 5:51 [PATCH 0/2] Use env for all perl invocations Pat Pannuto
2017-01-12 5:51 ` [PATCH 1/2] Convert all 'perl -w' to 'perl' + 'use warnings;' Pat Pannuto
2017-01-12 5:51 ` [PATCH 2/2] Use 'env' to find perl instead of fixed path Pat Pannuto
2017-01-12 6:27 ` Johannes Sixt
2017-01-12 7:17 ` Pat Pannuto
2017-01-12 10:21 ` Johannes Schindelin
2017-01-12 20:40 ` Junio C Hamano
2017-01-12 21:01 ` Pat Pannuto
2017-01-12 21:49 ` Junio C Hamano
2017-01-13 2:48 ` Eric Wong
2017-01-13 15:27 ` Johannes Schindelin
2017-01-13 16:58 ` Eric Wong
2017-01-13 17:13 ` Johannes Schindelin
2017-01-13 18:27 ` Junio C Hamano
2017-01-13 18:52 ` Eric Wong
2017-01-13 20:01 ` Junio C Hamano
2017-01-13 21:39 ` Eric Wong
2017-01-14 7:54 ` Jeff King
2017-01-14 10:31 ` Eric Wong
2017-01-14 21:57 ` brian m. carlson
2017-01-13 15:21 ` Johannes Schindelin [this message]
2017-01-12 6:21 ` [PATCH 0/2] Use env for all perl invocations Junio C Hamano
2017-01-12 7:13 ` Pat Pannuto
2017-01-12 8:21 ` 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=alpine.DEB.2.20.1701131621170.3469@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=pat.pannuto@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.