git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2021, #06; Sat, 30)
Date: Sun, 31 Jan 2021 12:52:37 -0800	[thread overview]
Message-ID: <xmqq7dnsomlm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20210131172107.GA2091@szeder.dev> ("SZEDER =?utf-8?Q?G=C3=A1?= =?utf-8?Q?bor=22's?= message of "Sun, 31 Jan 2021 18:21:07 +0100")

SZEDER Gábor <szeder.dev@gmail.com> writes:

> On Sat, Jan 30, 2021 at 04:00:56PM -0800, Junio C Hamano wrote:
>> [Stalled]
>> 
>> * sg/t7800-difftool-robustify (2021-01-09) 1 commit
>>  - t7800-difftool: don't accidentally match tmp dirs
>> 
>>  Test fix.
>> 
>>  Not working on Windows.
>>  cf. https://github.com/git/git/runs/1660588243?check_suite_focus=true#step:7:4186
>
> I think v2 of this patch fixed the test failure on Windows.

Ah, I missed that.  Yes, there are all-green runs on seen and this
topic is certainly part of it.

Let's merge it down.  Thanks for spotting.

  reply	other threads:[~2021-01-31 20:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  0:00 What's cooking in git.git (Jan 2021, #06; Sat, 30) Junio C Hamano
2021-01-31  1:42 ` Taylor Blau
2021-01-31 20:50   ` Junio C Hamano
2021-01-31 17:21 ` SZEDER Gábor
2021-01-31 20:52   ` Junio C Hamano [this message]
2021-01-31 20:11 ` Derrick Stolee
2021-01-31 20:53   ` Junio C Hamano
2021-02-01  0:27 ` Ævar Arnfjörð Bjarmason
2021-02-01  1:48   ` Junio C Hamano
2021-02-02 15:54     ` Johannes Schindelin
2021-02-02 20:18       ` Junio C Hamano
2021-02-01 15:51 ` Charvi Mendiratta
2021-02-01 19:48   ` Junio C Hamano
2021-02-02 15:28     ` Charvi Mendiratta
2021-02-03  1:08 ` Đoàn Trần Công Danh
2021-02-03  1:22   ` Junio C Hamano
2021-02-03 22:00     ` Miriam R.
2021-02-04  1:38       ` 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=xmqq7dnsomlm.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=szeder.dev@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 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).