From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [RFC] test-lib.sh: preprocess to use PERL_PATH
Date: Sat, 23 Jun 2012 07:26:10 +0200 [thread overview]
Message-ID: <4FE55372.3080008@web.de> (raw)
In-Reply-To: <7vsjdmli06.fsf@alter.siamese.dyndns.org>
On 23.06.12 07:22, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> All test cases found in t/*.sh must include test-lib instead of test-lib.sh
> Please don't. That is too much churning for too little gain, I am afraid.
Ok, would it be better to rename
t/test-lib.sh -> t/test-lib.sh.sh
and let the Makefile generate t/test-lib.sh?
next prev parent reply other threads:[~2012-06-23 5:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 5:04 [RFC] test-lib.sh: preprocess to use PERL_PATH Torsten Bögershausen
2012-06-23 5:22 ` Junio C Hamano
2012-06-23 5:26 ` Torsten Bögershausen [this message]
2012-06-23 6:18 ` Junio C Hamano
2012-06-23 13:11 ` Torsten Bögershausen
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=4FE55372.3080008@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).