From: Junio C Hamano <gitster@pobox•com>
To: Duy Nguyen <pclouds@gmail•com>
Cc: Karsten Blees <blees@dcon•de>,
Git Mailing List <git@vger•kernel.org>, Jeff King <peff@peff•net>
Subject: Re: What's cooking in git.git (Oct 2013, #06; Fri, 25)
Date: Mon, 28 Oct 2013 08:48:44 -0700 [thread overview]
Message-ID: <xmqq61shgzvn.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8A3s4TUmUOC+i-k97GxxvBQ7mQmdoPJizfy1yS3rqLEkA@mail.gmail.com> (Duy Nguyen's message of "Sat, 26 Oct 2013 17:30:42 +0700")
Duy Nguyen <pclouds@gmail•com> writes:
> On Sat, Oct 26, 2013 at 6:23 AM, Junio C Hamano <gitster@pobox•com> wrote:
>> * 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..
Good thinking ;-).
next prev parent reply other threads:[~2013-10-28 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 23:23 What's cooking in git.git (Oct 2013, #06; Fri, 25) Junio C Hamano
2013-10-26 10:30 ` Duy Nguyen
2013-10-28 15:48 ` Junio C Hamano [this message]
2013-10-28 16:16 ` Vicent Martí
2013-10-28 16:41 ` Junio C Hamano
2013-10-28 19:45 ` Karsten Blees
2013-10-28 21:04 ` Vicent Martí
2013-10-29 9:09 ` Karsten Blees
2013-11-14 19:38 ` Karsten Blees
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=xmqq61shgzvn.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=blees@dcon$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=pclouds@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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