The earlier description of the '-<n>' option was misleading- the user would have expected to be able to use it to limit the number of commits shown when specifying a revision range, for example. In reality, the option simply instructs the log to walk the topmost <n> commits. Also update the meaning of the same option in the git-format-patch documentation. Signed-off-by: Ramkumar Ramachandra <artagnon@xxxxxxxxx> --- Documentation/git-format-patch.txt | 2 +- Documentation/git-log.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index 4b3f5ba..df77474 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -74,7 +74,7 @@ OPTIONS include::diff-options.txt[] -<n>:: - Limits the number of patches to prepare. + Prepare patches from the topmost <n> commits. -o <dir>:: --output-directory <dir>:: diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt index 83e4ee3..ca02206 100644 --- a/Documentation/git-log.txt +++ b/Documentation/git-log.txt @@ -28,7 +28,7 @@ OPTIONS ------- -<n>:: - Limits the number of commits to show. + Show the topmost <n> commits. <since>..<until>:: Show only commits between the named two commits. When -- 1.7.2.2.409.gdbb11.dirty -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html