aboutsummaryrefslogtreecommitdiff
path: root/Documentation/gitdiffcore.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2010-09-29 13:49:03 -0700
committerJunio C Hamano <gitster@pobox.com>2010-09-29 13:49:03 -0700
commitb3c16ee454effda5ec8033ab665249710f622699 (patch)
tree9c50b0b2452c5332e7f37d769f5eec5484499e0e /Documentation/gitdiffcore.txt
parentae893e097ecbcbd8c6bea50017eb8cedddc5eaba (diff)
parentbf1dfc31032bf6195be63dd92d0b67906e4ff4f8 (diff)
downloadgit-b3c16ee454effda5ec8033ab665249710f622699.tar.xz
Merge branch 'jc/pickaxe-grep'
* jc/pickaxe-grep: diff/log -G<pattern>: tests git log/diff: add -G<regexp> that greps in the patch text diff: pass the entire diff-options to diffcore_pickaxe() gitdiffcore doc: update pickaxe description
Diffstat (limited to 'Documentation/gitdiffcore.txt')
-rw-r--r--Documentation/gitdiffcore.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/gitdiffcore.txt b/Documentation/gitdiffcore.txt
index 5d91a7e5b3..6af29a4603 100644
--- a/Documentation/gitdiffcore.txt
+++ b/Documentation/gitdiffcore.txt
@@ -227,9 +227,9 @@ changes that touch a specified string, and is controlled by the
commands.
When diffcore-pickaxe is in use, it checks if there are
-filepairs whose "result" side has the specified string and
-whose "origin" side does not. Such a filepair represents "the
-string appeared in this changeset". It also checks for the
+filepairs whose "result" side and whose "origin" side have
+different number of specified string. Such a filepair represents
+"the string appeared in this changeset". It also checks for the
opposite case that loses the specified string.
When `\--pickaxe-all` is not in effect, diffcore-pickaxe leaves