user/sven/git.git/diffcore.h, branch v1.4.4.4

diff.c: do not use pathname comparison to tell renames

2006-08-03T21:41:53Z

The final output from diff used to compare pathnames between preimage and postimage to tell if the filepair is a rename/copy. By explicitly marking the filepair created by diffcore_rename(), the output routine, resolve_rename_copy(), does not have to do so anymore. This helps feeding a filepair that has different pathnames in one and two elements to the diff machinery (most notably, comparing two blobs). Signed-off-by: Junio C Hamano

diffcore-rename: somewhat optimized.

2006-03-12T11:22:10Z

This changes diffcore-rename to reuse statistics information gathered during similarity estimation, and updates the hashtable implementation used to keep track of the statistics to be denser. This seems to give better performance. Signed-off-by: Junio C Hamano

diffcore-break: similarity estimator fix.

2006-03-04T21:26:36Z

This is a companion patch to the previous fix to diffcore-rename. The merging-back process should use a logic similar to what is used there. Signed-off-by: Junio C Hamano

diffcore-rename: split out the delta counting code.

2006-03-01T04:20:04Z

This is to rework diffcore break/rename/copy detection code so that it does not affected when deltifier code gets improved. Signed-off-by: Junio C Hamano

diffcore-break/diffcore-rename: integer overflow.

2006-01-16T05:08:42Z

While reviewing the end user tutorial rewrite by J. Bruce Fields, I noticed that "git-diff-tree -B -C" did not correctly break the total rewrite of Documentation/tutorial.txt. It turns out that we had integer overflow during the break score computations. Cop out by using floating point. This is not a kernel. Signed-off-by: Junio C Hamano

Diff: -l to limit rename/copy detection.

2005-09-25T06:50:44Z

When many paths are modified, rename detection takes a lot of time. The new option -l can be used to disable rename detection when more than paths are possibly created as renames. Signed-off-by: Junio C Hamano

Revert "[PATCH] plug memory leak in diff.c::diff_free_filepair()"

2005-09-14T21:06:50Z

This reverts 068eac91ce04b9aca163acb1927c3878c45d1a07 commit.

[PATCH] plug memory leak in diff.c::diff_free_filepair()

2005-08-14T01:28:55Z

When I run git-diff-tree on big change, it seems the command eats so much memory. so I just put git under valgrind to see what's going on. diff_free_filespec_data() doesn't free diff_filespec itself. [jc: I ended up doing things slightly differently from Yasushi's patch. The original idea was to use free_filespec_data() only to free the data portion and keep useing the filespec itself, but no existing code seems to do things that way, so I just yanked that part out.] Signed-off-by: Yasushi SHOJI Signed-off-by: Junio C Hamano

[PATCH] Re-Fix SIGSEGV on unmerged files in git-diff-files -p

2005-06-13T03:29:31Z

When an unmerged path was fed via diff_unmerged() into diffcore, it eventually called run_diff() with "one" and "two" parameters with NULL, but run_diff() was not written carefully enough to notice this situation. Signed-off-by: Junio C Hamano Signed-off-by: Linus Torvalds

Fix SIGSEGV on unmerged files in git-diff-files -p

2005-06-08T18:31:53Z

NULL is not considered a VALID pathspec.