From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #06)
Date: Wed, 21 Jan 2026 07:26:40 -0800 [thread overview]
Message-ID: <xmqqtswfvvf3.fsf@gitster.g> (raw)
In-Reply-To: <97d8645b-bae8-7f5c-8e59-0f4f0efd92f5@gmx.de> (Johannes Schindelin's message of "Wed, 21 Jan 2026 11:08:45 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> ...
>> - 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.
next prev parent reply other threads:[~2026-01-21 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 12:10 What's cooking in git.git (Jan 2026, #06) Junio C Hamano
2026-01-20 15:01 ` Shreyansh Paliwal
2026-01-20 16:30 ` Junio C Hamano
2026-01-21 10:08 ` Johannes Schindelin
2026-01-21 15:26 ` Junio C Hamano [this message]
2026-01-21 16:20 ` Junio C Hamano
2026-01-21 16:14 ` Phillip Wood
2026-01-21 19:54 ` Samuel Abraham
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=xmqqtswfvvf3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--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