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

Re: What's cooking in git.git (Oct 2013, #06; Fri, 25)

From
Duy Nguyen <pclouds@gmail.com>
Date
Oct 26, 2013, 10:30 UTC
Message-ID
<CACsJy8A3s4TUmUOC+i-k97GxxvBQ7mQmdoPJizfy1yS3rqLEkA@mail.gmail.com>
In-Reply-To
<xmqqeh79hr3o.fsf@gitster.dls.corp.google.com>
On Sat, Oct 26, 2013 at 6:23 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 20 quoted lines
> * kb/fast-hashmap (2013-10-22) 12 commits
>  - remove old hash.[ch] implementation
>  - read-cache.c: fix memory leaks caused by removed cache entries
>  - name-hash.c: remove cache entries instead of marking them CE_UNHASHED
>  - name-hash.c: use new hash map implementation for cache entries
>  - name-hash.c: remove unreferenced directory entries
>  - name-hash.c: use new hash map implementation for directories
>  - diffcore-rename.c: use new hash map implementation
>  - diffcore-rename.c: simplify finding exact renames
>  - diffcore-rename.c: move code around to prepare for the next patch
>  - buitin/describe.c: use new hash map implementation
>  - add a hashtable implementation that supports O(1) removal
>  - submodule: don't access the .gitmodules cache entry after removing it
>
>  Improvements to our hash table to get it to meet the needs of the
>  msysgit fscache project, with some nice performance improvements.
>
>  The preparatory clean-up to submodule from Jens is at the bottom. I
>  also squashed in a fix-up by Karsten found at $gmane/236468 (please
>  double-check the result).

jk/pack-bitmap adds khash.h, which from a first glance looks like yet another hash table implementation. I was just wondering if kb's new hash tables can cover the need of pack-bitmap.c too so we can remove khash.h later..

-- 
Duy
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 9 in “What's cooking in git.git (Oct 2013, #06; Fri, 25)”
  1. Junio C HamanoOct 25, 2013
  2. Duy NguyenOct 26, 2013
  3. Junio C HamanoOct 28, 2013
  4. Vicent MartíOct 28, 2013
  5. Junio C HamanoOct 28, 2013
  6. Karsten BleesOct 28, 2013
  7. Vicent MartíOct 28, 2013
  8. Karsten BleesOct 29, 2013
  9. Karsten BleesNov 14, 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.