From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Thomas Rast" <tr@thomasrast.ch>,
"Derrick Stolee" <stolee@gmail.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: [PATCH 0/2] line-log: avoid unnecessary full tree diffs
Date: Wed, 21 Aug 2019 13:04:22 +0200 [thread overview]
Message-ID: <20190821110424.18184-1-szeder.dev@gmail.com> (raw)
Line-level log can be very slow with rename detection enabled (and its
enabled by default), which is caused by it using the diff machinery
very inefficiently. The second patch fixes the issue and make it much
faster, especially in large repositories.
This patch series is independent from my other patch series making
line-level log incremental [1]. The two can be merged easily, as the
changes to 'line-log.c' don't overlap, and the conflict in
't4211-line-log.sh' is trivial (both series add new tests at the end
of that test script).
[1] https://public-inbox.org/git/6a576e13-79e6-43be-c4a8-065e7a8310ea@gmail.com/T/
SZEDER Gábor (2):
line-log: extract pathspec parsing from line ranges into a helper
function
line-log: avoid unnecessary full tree diffs
line-log.c | 71 ++++++++++++++++++++++++++++-----------
t/t4211-line-log.sh | 82 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 134 insertions(+), 19 deletions(-)
--
2.23.0.352.gebb2b55eae
next reply other threads:[~2019-08-21 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 11:04 SZEDER Gábor [this message]
2019-08-21 11:04 ` [PATCH 1/2] line-log: extract pathspec parsing from line ranges into a helper function SZEDER Gábor
2019-08-21 11:04 ` [PATCH 2/2] line-log: avoid unnecessary full tree diffs SZEDER Gábor
2019-08-21 15:53 ` Derrick Stolee
2019-08-21 17:35 ` SZEDER Gábor
2019-08-21 18:12 ` Derrick Stolee
2019-08-22 8:41 ` SZEDER Gábor
2019-08-22 14:53 ` Derrick Stolee
2019-08-22 16:01 ` Junio C Hamano
2019-08-22 16:26 ` SZEDER Gábor
2019-08-22 16:51 ` Derrick Stolee
2019-08-23 10:04 ` SZEDER Gábor
2019-08-21 17:29 ` Junio C Hamano
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=20190821110424.18184-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=stolee@gmail.com \
--cc=tr@thomasrast.ch \
/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).