From: Jonathan Tan <jonathantanmy@google.com>
To: git@vger.kernel.org
Cc: Jonathan Tan <jonathantanmy@google.com>, stolee@gmail.com
Subject: [PATCH 0/2] Refactor hash search with fanout table
Date: Fri, 2 Feb 2018 14:36:29 -0800 [thread overview]
Message-ID: <cover.1517609773.git.jonathantanmy@google.com> (raw)
After reviewing Derrick's Serialized Git Commit Graph patches [1], I
noticed that "[PATCH v2 11/14] commit: integrate commit graph with
commit parsing" contains (in bsearch_graph) a repeat of some packfile
functionality. Here is a pack that refactors that functionality out.
Derrick, consider incorporating these patches in your next reroll.
[1] https://public-inbox.org/git/1517348383-112294-1-git-send-email-dstolee@microsoft.com/
Jonathan Tan (2):
packfile: remove GIT_DEBUG_LOOKUP log statements
packfile: refactor hash search with fanout table
packfile.c | 30 +++++-------------------------
sha1-lookup.c | 24 ++++++++++++++++++++++++
sha1-lookup.h | 21 +++++++++++++++++++++
3 files changed, 50 insertions(+), 25 deletions(-)
--
2.16.0.rc1.238.g530d649a79-goog
next reply other threads:[~2018-02-02 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 22:36 Jonathan Tan [this message]
2018-02-02 22:36 ` [PATCH 1/2] packfile: remove GIT_DEBUG_LOOKUP log statements Jonathan Tan
2018-02-02 22:36 ` [PATCH 2/2] packfile: refactor hash search with fanout table Jonathan Tan
2018-02-09 18:03 ` René Scharfe
2018-02-09 19:50 ` Jonathan Tan
2018-02-02 23:30 ` [PATCH 0/2] Refactor " Junio C Hamano
2018-02-03 2:09 ` Derrick Stolee
2018-02-13 18:39 ` [PATCH v2 " Jonathan Tan
2018-02-13 18:39 ` [PATCH v2 1/2] packfile: remove GIT_DEBUG_LOOKUP log statements Jonathan Tan
2018-02-13 18:39 ` [PATCH v2 2/2] packfile: refactor hash search with fanout table Jonathan Tan
2018-02-13 18:52 ` [PATCH v2 0/2] Refactor " Derrick Stolee
2018-02-13 19:57 ` Junio C Hamano
2018-02-13 20:15 ` Jonathan Tan
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=cover.1517609773.git.jonathantanmy@google.com \
--to=jonathantanmy@google.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.