From: Michael J Gruber <git@drmicha•warpmail.net>
To: Kacper Kornet <draenog@pld-linux•org>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: [PATCH] t1507: change quoting in test_did_you_mean to a more general one
Date: Fri, 06 May 2011 11:14:19 +0200 [thread overview]
Message-ID: <4DC3BBEB.1050502@drmicha.warpmail.net> (raw)
In-Reply-To: <20110506085107.GB3719@camk.edu.pl>
Kacper Kornet venit, vidit, dixit 06.05.2011 10:51:
> On Fri, May 06, 2011 at 09:43:01AM +0200, Michael J Gruber wrote:
>> Junio C Hamano venit, vidit, dixit 05.05.2011 22:02:
>>> Kacper Kornet <draenog@pld-linux•org> writes:
>>>> Signed-off-by: Kacper Kornet <draenog@pld-linux•org>
>>>> ---
>>>> t/t1506-rev-parse-diagnosis.sh | 4 ++--
>>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>
>>>> diff --git a/t/t1506-rev-parse-diagnosis.sh b/t/t1506-rev-parse-diagnosis.sh
>>>> index 4a6396f..bad09f9 100755
>>>> --- a/t/t1506-rev-parse-diagnosis.sh
>>>> +++ b/t/t1506-rev-parse-diagnosis.sh
>>>> @@ -8,8 +8,8 @@ exec </dev/null
>
>>>> test_did_you_mean ()
>>>> {
>>>> - printf "fatal: Path '$2$3' $4, but not ${5:-'$3'}.\n" >expected &&
>>>> - printf "Did you mean '$1:$2$3'${2:+ aka '$1:./$3'}?\n" >>expected &&
>>>> + printf "fatal: Path '$2$3' $4, but not ${5:-\'$3\'}.\n" >expected &&
>>>> + printf "Did you mean '$1:$2$3'${2:+ aka \'$1:./$3\'}?\n" >>expected &&
>>>> test_cmp expected error
>>>> }
>
>>>> --
>>>> 1.7.5
>
>>> [Reference]
>
>>> *1* http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_06_02
>
>> Other than that, I have no objections if this patch makes more shells
>> happy and no happy ones unhappy.
>
>> Is your ksh OK with all other tests?
>
> Yes. The only other patch which is applied during our building process
> is:
>
> diff -ur git-1.7.0.3.orig/t/t1304-default-acl.sh
> git-1.7.0.3/t/t1304-default-acl
> .sh
> --- git-1.7.0.3.orig/t/t1304-default-acl.sh 2010-03-22
> 01:35:03.000000000 +0
> 000
> +++ git-1.7.0.3/t/t1304-default-acl.sh 2010-03-23 19:53:49.069813289
> +0000
> @@ -9,6 +9,8 @@
> # => this must come before . ./test-lib.sh
> umask 077
>
> +LOGNAME=$(whoami)
> +
> . ./test-lib.sh
>
> # We need an arbitrary other user give permission to using ACLs. root
>
>
> But it is specific to our build environment.
>
Thanks for the info (and for responding despite my botched to/cc).
In a different context I noticed that systems don't agree wrt. the
presence of USER/USERNAME/LOGNAME in the environment. We use LOGNAME in
t1304 only (and never USER nor USERNAME), but still we might want to do
something like
LOGNAME=${LOGNAME:-$USERNAME}
LOGNAME=${LOGNAME:-$USER}
LOGNAME=${LOGNAME:-$(whoami)}
there, or simpler with ${LOGNAME:=...}, although I don't know what to
take for granted.
Michael
next prev parent reply other threads:[~2011-05-06 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 19:10 [PATCH] t1507: change quoting in test_did_you_mean to a more general one Kacper Kornet
2011-05-05 20:02 ` Junio C Hamano
2011-05-06 7:43 ` Michael J Gruber
2011-05-06 8:51 ` Kacper Kornet
2011-05-06 9:14 ` Michael J Gruber [this message]
2011-05-06 10:22 ` Johannes Sixt
2011-05-06 11:10 ` Michael J Gruber
2011-05-06 14:23 ` Junio C Hamano
2011-05-09 4:40 ` Junio C Hamano
2011-05-09 6:39 ` Johannes Sixt
2011-05-09 16:20 ` Junio C Hamano
2011-05-06 8:39 ` Kacper Kornet
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=4DC3BBEB.1050502@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=draenog@pld-linux$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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