git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] name-hash: don't add sparse directories in threaded lazy init

From
Alex Mironov <alexandrfox@gmail.com>
Date
May 21, 2025, 21:40 UTC
Message-ID
<CAC97Eby+FQd3p5YVqgvvaYuxKD1yoUPWJ7RSuFNd4Gd92+ZSxg@mail.gmail.com>
In-Reply-To
<xmqqjz698xqb.fsf@gitster.g>
Dear Junio,

Thank you for the feedback, I adjusted the commit message in full which hopefully makes this patch clearer. At the same time I don't quite understand the need for the perceived hostility - this is not some "fuzzy" words, but the messaging from the original author of the sparse feature. I certainly understand your desire to uphold the standards of contributions to git, especially from the new author, but I must say I feel quite alienated by your reply.

Nonetheless, the adjustment is submitted now and I hope that further contributions remain welcomed.

On Wed, May 21, 2025 at 11:23 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 38 quoted lines
>
> 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.

-- Best, Alex Mironov

Previous: Junio C HamanoNext: Alex Mironov via GitGitGadget
Message 10 of 13 in “name-hash: don't add sparse directories in threaded lazy init”
  1. name-hash: don't add sparse directories in threaded lazy initAlex Mironov via GitGitGadget, May 21, 2025
  2. Derrick StoleeMay 21, 2025
  3. Junio C HamanoMay 21, 2025
  4. Alex MironovMay 21, 2025
  5. name-hash: don't add sparse directories in threaded lazy initAlex Mironov via GitGitGadget, May 21, 2025
  6. Junio C HamanoMay 21, 2025
  7. Alex MironovMay 21, 2025
  8. Junio C HamanoMay 21, 2025
  9. Junio C HamanoMay 21, 2025
  10. Alex MironovMay 21, 2025
  11. name-hash: don't add sparse directories in threaded lazy initAlex Mironov via GitGitGadget, May 21, 2025
  12. Junio C HamanoMay 21, 2025
  13. Derrick StoleeMay 22, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.