sapling/tests/test-addremove-similar.out

adding empty-file
adding large-file
adding another-file
removing empty-file
removing large-file
recording removal of large-file as rename to another-file (99% similar)
adding large-file
adding tiny-file
adding small-file
removing large-file
removing tiny-file
recording removal of tiny-file as rename to small-file (82% similar)
Avoid some false positives for addremove -s The original code uses the similary score 1 - len(diff(after, before)) / len(after) The diff can at most be the size of the 'before' file, so any small 'before' file would be considered very similar. Removing an empty file would cause all files added in the same revision to be considered copies of the removed file. This changes the metric to bytes_overlap(before, after) / len(before + after) i.e. the actual percentage of bytes shared between the two files. 2007-02-18 22:39:25 +03:00			`adding empty-file`
			`adding large-file`
			`adding another-file`
			`removing empty-file`
			`removing large-file`
			`recording removal of large-file as rename to another-file (99% similar)`
			`adding large-file`
			`adding tiny-file`
			`adding small-file`
			`removing large-file`
			`removing tiny-file`
			`recording removal of tiny-file as rename to small-file (82% similar)`