Re: What's cooking in git.git (Jan 2026, #06)

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 21, 2026, 15:26 UTC
Message-ID: <xmqqtswfvvf3.fsf@gitster.g>
In-Reply-To: <97d8645b-bae8-7f5c-8e59-0f4f0efd92f5@gmx.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 19 quoted lines

>>  ...
>>  - Merge branch 'js/prep-symlink-windows' into js/symlink-windows
>>  (this branch uses js/prep-symlink-windows.)
>> 
>>  Upstream symbolic link support on Windows from Git-for-Windows.
>> 
>>  Expecting a reroll.
>>  cf. <5fe64b77-d10b-b66e-8622-14bec1e96f4a@gmx.de>
>>  cf. <14388349-d1b5-fc8f-b6c7-4a7b43e64494@gmx.de>
>>  cf. <704e952d-7924-00ce-b8b0-ad355e659335@gmx.de>
>>  source: <pull.2018.v2.git.1767989115.gitgitgadget@gmail.com>
>
> I do not quite understand.
>
> v2 was sent out on Jan 9. The three replies you are referring to as
> blockers were all sent out on the same day, as replies to the respective
> reviewer comments in v1. Naturally, whan I did sent out those replies
> acknowleding problems whose fixes I promised, I did not then go on and
> omit the fixes from v2!

Sorry, my mistake. It is very possible that the references may be stale for this topic, as I can forget update them when I queue a newer iteration.

Will take a look later today.  Thanks.