From: Junio C Hamano <gitster@pobox.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, congdanhqx@gmail.com
Subject: Re: [PATCH] t/test_lib: avoid naked bash arrays in file_lineno
Date: Thu, 07 May 2020 18:17:25 -0700 [thread overview]
Message-ID: <xmqqpnbf1aze.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200508005817.GA24664@Carlos-MBP> ("Carlo Marcelo Arenas Belón"'s message of "Thu, 7 May 2020 17:58:17 -0700")
Carlo Marcelo Arenas Belón <carenas@gmail.com> writes:
> On Thu, May 07, 2020 at 09:52:12PM +0200, Johannes Schindelin wrote:
>> On Wed, 6 May 2020, Carlo Marcelo Arenas Belón wrote:
>> >
>> > Enclose the bash specific code inside an eval to avoid parsing errors
>> > and while at it, simplify the logic so that instead of traversing the
>> > callstack just pop the two topmost entries that are required.
>>
>> I would be okay with that, but that's not what the patch does:
>
> FWIW that was the intention, but luckily Junio quickly predicted it was
> most likely buggy and so has been since made obsolete by:
>
> https://lore.kernel.org/git/20200507175706.19986-1-carenas@gmail.com/
Heh, don't give me too much credit. I just noticed that they cannot
be implementing the same thing, but I couldn't tell if the new
behaviour was something you two agreed to be better, and asked for a
clarification.
In any case, the "just protect with eval '' block to avoid hurting
other shells" version should be the first step. Improving it
further is a separate topic.
Thanks.
prev parent reply other threads:[~2020-05-08 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 5:51 [PATCH] t/test_lib: avoid naked bash arrays in file_lineno Carlo Marcelo Arenas Belón
2020-05-07 14:53 ` Junio C Hamano
2020-05-07 17:33 ` Carlo Arenas
2020-05-07 17:57 ` Carlo Marcelo Arenas Belón
2020-05-08 23:53 ` Johannes Schindelin
2020-05-07 19:52 ` Johannes Schindelin
2020-05-08 0:58 ` Carlo Marcelo Arenas Belón
2020-05-08 1:17 ` Junio C Hamano [this message]
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=xmqqpnbf1aze.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=carenas@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
/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).