From: Junio C Hamano <gitster@pobox.com>
To: Alex Mironov <alexandrfox@gmail.com>
Cc: Alex Mironov via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH v2] name-hash: don't add sparse directories in threaded lazy init
Date: Wed, 21 May 2025 14:23:08 -0700 [thread overview]
Message-ID: <xmqqjz698xqb.fsf@gitster.g> (raw)
In-Reply-To: <xmqqo6vl8y81.fsf@gitster.g> (Junio C. Hamano's message of "Wed, 21 May 2025 14:12:30 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Alex Mironov <alexandrfox@gmail.com> writes:
>
>> Hey Junio,
>>
>> With respect to messaging I more or less copy-pasted Derricks message
>> from the original commit for non-threaded init: please check the
>> referenced commit. Let me know if another wording is needed/preferred.
>
> I know what you did. Copying and pasting others fuzzy words into
> your commit log message does not make your commit log message clear.
>
> I already said the given message is less clear than desired, so do I
> still have to let you know???
Actually after re-reading what Derrick wrote in that commit, I
notice that you didn't even copy-pasted his message in full. Here
is the message in 5f116695 (name-hash: don't add directories to
name_hash, 2021-04-12):
name-hash: don't add directories to name_hash
Sparse directory entries represent a directory that is outside the
sparse-checkout definition. These are not paths to blobs, so should not
be added to the name_hash table. Instead, they should be added to the
directory hashtable when 'ignore_case' is true.
Add a condition to avoid placing sparse directories into the name_hash
hashtable. This avoids filling the table with extra entries that will
never be queried.
Notice that the second paragraph here makes it clear that how extra
entries would not contribute to or hurt the correctness? You failed
to copy-paste that crucial bit, which ended up making your version
of the explanation much less clear why the change would not affect
correctness than it could have been.
next prev parent reply other threads:[~2025-05-21 21:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 11:40 [PATCH] name-hash: don't add sparse directories in threaded lazy init Alex Mironov via GitGitGadget
2025-05-21 17:17 ` Derrick Stolee
2025-05-21 18:32 ` Junio C Hamano
2025-05-21 20:07 ` Alex Mironov
2025-05-21 20:16 ` [PATCH v2] " Alex Mironov via GitGitGadget
2025-05-21 20:32 ` Junio C Hamano
2025-05-21 20:37 ` Alex Mironov
2025-05-21 21:12 ` Junio C Hamano
2025-05-21 21:23 ` Junio C Hamano [this message]
2025-05-21 21:40 ` Alex Mironov
2025-05-21 21:29 ` [PATCH v3] " Alex Mironov via GitGitGadget
2025-05-21 21:47 ` Junio C Hamano
2025-05-22 1:48 ` Derrick Stolee
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=xmqqjz698xqb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alexandrfox@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=stolee@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).