From: Ralf Wildenhues Date: Thu, 01 Nov 2007 08:45:53 GMT Subject: [PATCH] git-rev-list.txt: rev stands for revision, not reverse. Message-ID: <20071101084552.GA4934@ins.uni-bonn.de> Mention revs, revisions as aliases for commit objects, to clarify that rev-list is not an abbreviation for listing in reverse order, but for listing revisions. --- Yes, believe it or not, but I stumbled over the synopsis | git-rev-list - Lists commit objects in reverse chronological order asking myself whether rev could possibly mean "reverse". I hope this helps avoid this pitfall for others. Cheers, Ralf Documentation/git-rev-list.txt | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt index 4852804..8afe34b 100644 --- a/Documentation/git-rev-list.txt +++ b/Documentation/git-rev-list.txt @@ -44,9 +44,9 @@ SYNOPSIS DESCRIPTION ----------- -Lists commit objects in reverse chronological order starting at the -given commit(s), taking ancestry relationship into account. This is -useful to produce human-readable log output. +Lists commit objects (revs, revisions) in reverse chronological order +starting at the given commit(s), taking ancestry relationship into +account. This is useful to produce human-readable log output. Commits which are stated with a preceding '{caret}' cause listing to stop at that point. Their parents are implied. Thus the following -- 1.5.3.3.g34c6d