object name: introduce ':/<oneline prefix>' notation

[git.git] / Documentation / git-whatchanged.txt

diff --git a/Documentation/git-whatchanged.txt b/Documentation/git-whatchanged.txt
index f02f939baa9183325d582cc12486a24f3d3ff30f..399bff3bbcab89be96039c373cf1120dcab0efe1 100644 (file)
--- a/Documentation/git-whatchanged.txt
+++ b/Documentation/git-whatchanged.txt
@@ -27,7 +27,7 @@ OPTIONS
        output format that is useful only to tell the changed
        paths and their nature of changes.
 
        output format that is useful only to tell the changed
        paths and their nature of changes.
 

---max-count=<n>::
+-<n>::

        Limit output to <n> commits.
 
 <since>..<until>::
        Limit output to <n> commits.
 
 <since>..<until>::


@@ -47,9 +47,9 @@ OPTIONS
        By default, differences for merge commits are not shown.
        With this flag, show differences to that commit from all
        of its parents.
        By default, differences for merge commits are not shown.
        With this flag, show differences to that commit from all
        of its parents.

-
-       However, it is not very useful in general, although it
-       *is* useful on a file-by-file basis.
++
+However, it is not very useful in general, although it
+*is* useful on a file-by-file basis.

 
 Examples
 --------
 
 Examples
 --------


@@ -58,7 +58,7 @@ git-whatchanged -p v2.6.12.. include/scsi drivers/scsi::
        Show as patches the commits since version 'v2.6.12' that changed
        any file in the include/scsi or drivers/scsi subdirectories
 
        Show as patches the commits since version 'v2.6.12' that changed
        any file in the include/scsi or drivers/scsi subdirectories
 

-git-whatchanged --since="2 weeks ago" -- gitk::
+git-whatchanged --since="2 weeks ago" \-- gitk::

 
        Show the changes during the last two weeks to the file 'gitk'.
        The "--" is necessary to avoid confusion with the *branch* named
 
        Show the changes during the last two weeks to the file 'gitk'.
        The "--" is necessary to avoid confusion with the *branch* named