From: Junio C Hamano <gitster@pobox.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [ANNOUNCE] Git v2.27.0-rc0
Date: Wed, 20 May 2020 07:37:53 -0700 [thread overview]
Message-ID: <xmqq8shmy8n2.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <CA+kUOam31cLNftUx6rGz=bdpjo5Dqv_ahJ6jUnD8OGq6P6Ra3w@mail.gmail.com> (Adam Dinwoodie's message of "Wed, 20 May 2020 15:14:17 +0100")
Adam Dinwoodie <adam@dinwoodie.org> writes:
> On Wed, 20 May 2020 at 00:21, Junio C Hamano <gitster@pobox.com> wrote:
>> Adam Dinwoodie <adam@dinwoodie.org> writes:
>>
>> >> tests: when run in Bash, annotate test failures with file name/line number
>> >
>> > At least on Cygwin, this breaks the test output parsing of failures
>> > when running with prove.
>>
>> We'll revert this problematic topic out (which hasn't happened yet),
>> which I hopefully will be able to merge to 'master' before tagging
>> the -rc1 release candidate.
>>
>> If possible, could you test the result of merging e31600b0 (Revert
>> "tests: when run in Bash, annotate test failures with file name/line
>> number", 2020-05-15) into 'master'?
>
> I get a merge conflict due to 303775a25f ("t/test_lib: avoid naked
> bash arrays in file_lineno", 2020-05-07), but resolving that in the
> obvious fashion and the test summaries are working as expected again.
Wonderful. Thanks.
next prev parent reply other threads:[~2020-05-20 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 23:27 [ANNOUNCE] Git v2.27.0-rc0 Junio C Hamano
2020-05-15 14:21 ` Randall S. Becker
2020-05-15 14:57 ` Junio C Hamano
2020-05-19 19:10 ` Adam Dinwoodie
2020-05-19 23:21 ` Junio C Hamano
2020-05-20 14:14 ` Adam Dinwoodie
2020-05-20 14:37 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-14 23:28 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq8shmy8n2.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).