From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/5] Speeding up "git status" and "git diff --cached"
Date: Sat, 23 May 2009 12:24:33 -0700 [thread overview]
Message-ID: <1243106678-6343-1-git-send-email-gitster@pobox.com> (raw)
Here is a refined version of an earlier patch series to use cache-tree
information to optimize comparison between the index with an existing
commit.
Recently there was a discussion to auto-commit any change to the index
that are going to be discarded to some kind of "trash" branch; I am not
personally interested in writing a patch to do so, but this will also help
such a feature by making it cheaper to see if there are differences worth
saving.
Junio C Hamano (5):
write-tree --ignore-cache-tree
cache-tree.c::cache_tree_find(): simplify inernal API
t4007: modernize the style
Optimize "diff-index --cached" using cache-tree
Avoid "diff-index --cached" optimization under --find-copies-harder
builtin-write-tree.c | 12 ++++++--
cache-tree.c | 44 +++++++++++++++++++++++++++--
cache-tree.h | 10 ++++++-
diff-lib.c | 3 ++
t/t4007-rename-3.sh | 74 +++++++++++++++++++++++++-------------------------
unpack-trees.c | 17 +++++++++++
unpack-trees.h | 1 +
7 files changed, 117 insertions(+), 44 deletions(-)
next reply other threads:[~2009-05-23 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 19:24 Junio C Hamano [this message]
2009-05-23 19:24 ` [PATCH 1/5] write-tree --ignore-cache-tree Junio C Hamano
2009-05-23 19:24 ` [PATCH 2/5] cache-tree.c::cache_tree_find(): simplify inernal API Junio C Hamano
2009-05-23 19:24 ` [PATCH 3/5] t4007: modernize the style Junio C Hamano
2009-05-23 19:24 ` [PATCH 4/5] Optimize "diff-index --cached" using cache-tree Junio C Hamano
2009-05-23 19:24 ` [PATCH 5/5] Avoid "diff-index --cached" optimization under --find-copies-harder Junio C Hamano
2009-05-25 10:59 ` [PATCH 0/5] Speeding up "git status" and "git diff --cached" Jeff King
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=1243106678-6343-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).