git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-rev-list.txt: rev stands for revision, not reverse.

From
RWRalf Wildenhues <ralf.wildenhues@gmx.de>
Date
Nov 1, 2007, 08:45 UTC
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
Next: Junio C Hamano
Message 1 of 5 in “git-rev-list.txt: rev stands for revision, not reverse.”
  1. git-rev-list.txt: rev stands for revision, not reverse.Ralf Wildenhues, Nov 1, 2007
  2. Junio C HamanoNov 1, 2007
  3. Ralf WildenhuesNov 2, 2007
  4. Junio C HamanoNov 2, 2007
  5. Junio C HamanoNov 2, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.