diff options
author | Johan Herland <johan@herland.net> | 2010-09-30 20:15:14 +0200 |
---|---|---|
committer | Lars Hjemli <hjemli@gmail.com> | 2010-11-09 16:37:39 +0100 |
commit | 1415f3f3e017d0123e850707c55cb7e5e5887406 (patch) | |
tree | 9036ea6ce534e40ff35394359332a9a628276c0f /filters/syntax-highlighting.sh | |
parent | e0c6f23789e4893781bcd5af2281d468991ccf3a (diff) | |
download | cgit-1415f3f3e017d0123e850707c55cb7e5e5887406.tar.gz cgit-1415f3f3e017d0123e850707c55cb7e5e5887406.tar.bz2 cgit-1415f3f3e017d0123e850707c55cb7e5e5887406.zip |
ui-log: Fix filecount/linecount when path limit is in effect
When using ui-log with path limits, the listing of commits enables parent
rewriting in Git's internal log machinery. This did not work well together
with cgit_diff_commit() which is used to generate the filecount and
linecount numbers for each commit in the log view. cgit_diff_commit() would
operate without any path limits, and would therefore process the full diff
between the commits shown (which, because of parent rewriting, is not the
same as processing the diff for the commit itself). Additionally, the bottom
commit in the log view would (again, because of parent rewriting) have zero
parents, causing us to process the entire diff between the empty tree and
that commit. Since path limits were not in effect, this would (in large
projects) reports thousands of files and millions of lines changed in that
bottom commit.
This patch fixes the issue by applying the same path limit to
cgit_diff_commit() as is applied to the rest of the log view. The result is
that the filecount/linecount now only reflects the diff as it pertains to
the given path limit.
Signed-off-by: Johan Herland <johan@herland.net>
Signed-off-by: Lars Hjemli <hjemli@gmail.com>
Diffstat (limited to 'filters/syntax-highlighting.sh')
0 files changed, 0 insertions, 0 deletions