From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Teng Long <dyroneteng@gmail.com>,
bturner@atlassian.com, avarab@gmail.com, git@vger.kernel.org
Subject: Re: Git 2.36, ls-tree submodule regression?
Date: Thu, 07 Apr 2022 11:20:33 -0700 [thread overview]
Message-ID: <xmqqk0c0sqku.fsf@gitster.g> (raw)
In-Reply-To: nycvar.QRO.7.76.6.2204071436150.347@tvgsbejvaqbjf.bet
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Correction, it was fixed by Josh Steadmon, and Ævar proposed an
> alternative, but Josh's version made it into the `main` branch:
Correct, although the actual fixes were identical one-liner and it
didn't really matter in the end result where the fix was taken from.
prev parent reply other threads:[~2022-04-07 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 0:34 Git 2.36, ls-tree submodule regression? Bryan Turner
2022-04-07 1:29 ` Bryan Turner
2022-04-07 1:41 ` Bryan Turner
2022-04-07 2:22 ` Teng Long
2022-04-07 12:37 ` Johannes Schindelin
2022-04-07 18:20 ` 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=xmqqk0c0sqku.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=bturner@atlassian.com \
--cc=dyroneteng@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).