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

Re: Make GIT_USE_LOOKUP default?

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2013, 20:13 UTC
Message-ID
<7vd2uxrdh7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8AihriCDfN=cz7FjdHzZAhnPPGML_w8yWcVVrmTQLZyjw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
> This env comes from jc/sha1-lookup in 2008 (merge commit e9f9d4f), 5
> years ago. I wonder if it's good enough to turn on by default and keep
> improving from there, or is it still experimental?

The algorithm has been used in production in other codepaths like patch-ids and replace-object, so correctness-wise it should be fine to turn it on. I think nobody has bothered to benchmark with and without the environment to see if it is really worth the complexity.

It may be a good idea to try doing so, now you have noticed it ;-).
Previous: Duy NguyenNext: Jeff King
Message 2 of 10 in “Make GIT_USE_LOOKUP default?”
  1. Duy NguyenMar 17, 2013
  2. Junio C HamanoMar 17, 2013
  3. Jeff KingMar 18, 2013
  4. Junio C HamanoMar 18, 2013
  5. Jeff KingMar 18, 2013
  6. Junio C HamanoMar 18, 2013
  7. Jeff KingMar 18, 2013
  8. Junio C HamanoMar 18, 2013
  9. Duy NguyenMar 19, 2013
  10. Jeff KingMar 19, 2013

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.