Teach tree_entry_interesting() that the tree entries are sorted.

diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt
index c8bd1977790b2611d4b7974fc3a716d99b888a74..a7e9fd021a4cc1e467b2df7dd7e06d79a5182c7a 100644 (file)
--- a/Documentation/git-patch-id.txt
+++ b/Documentation/git-patch-id.txt
@@ -3,7 +3,7 @@ git-patch-id(1)
 
 NAME
 ----
-git-patch-id - Generate a patch ID.
+git-patch-id - Compute unique ID for a patch
 
 SYNOPSIS
 --------
@@ -13,7 +13,7 @@ DESCRIPTION
 -----------
 A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with
 whitespace and line numbers ignored.  As such, it's "reasonably stable", but at
-the same time also reasonably unique, ie two patches that have the same "patch
+the same time also reasonably unique, i.e., two patches that have the same "patch
 ID" are almost guaranteed to be the same thing.
 
 IOW, you can use this thing to look for likely duplicate commits.