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

[PATCH 5/7] git-log.txt: generalize <since>..<until>

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Apr 21, 2013, 08:50 UTC
Message-ID
<1366534252-12099-6-git-send-email-artagnon@gmail.com>
In-Reply-To
<1366534252-12099-1-git-send-email-artagnon@gmail.com>

'<since>..<until>' is misleading, as there are many other forms that 'git log' can accept as an argument. Replace it with <revision range>, referring to the section "Specifying Ranges" in revisions.txt, and rewrite the section appropriately.

Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
 Documentation/git-log.txt | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 64cc337..c238475 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -9,7 +9,7 @@ git-log - Show commit logs
 SYNOPSIS
 --------
 [verse]
-'git log' [<options>] [<since>..<until>] [[\--] <path>...]
+'git log' [<options>] [<revision range>] [[\--] <path>...]
 
 DESCRIPTION
 -----------
@@ -62,12 +62,14 @@ produced by --stat etc.
 	Note that only message is considered, if also a diff is shown
 	its size is not included.
 
-<since>..<until>::
-	Show only commits between the named two commits.  When
-	either <since> or <until> is omitted, it defaults to
-	`HEAD`, i.e. the tip of the current branch.
-	For a more complete list of ways to spell <since>
-	and <until>, see linkgit:gitrevisions[7].
+<revision range>::
+	Show only commits in the specified revision range.  When no
+	<revision range> is specified, it defaults to 'HEAD' (ie. the
+	whole history leading to the current commit).  master..HEAD
+	specifies all the commits reachable from 'HEAD', but not from
+	'master'. For a complete list of ways to spell
+	<revision range>, see the "Specifying Ranges" section of
+	linkgit:gitrevisions[7].
 
 [\--] <path>...::
 	Show only commits that are enough to explain how the files
-- 
1.8.2.1.501.gd2949c7
Previous: Ramkumar RamachandraNext: Junio C Hamano
Message 6 of 10 in “Documentation/shortlog improvements”
  1. 0/7 Documentation/shortlog improvementsRamkumar Ramachandra, Apr 21, 2013
  2. 1/7 git-shortlog.txt: remove (-h|--help) from OPTIONSRamkumar Ramachandra, Apr 21, 2013
  3. 2/7 builtin/shortlog.c: make usage string consistent with logRamkumar Ramachandra, Apr 21, 2013
  4. 3/7 revisions.txt: clarify the .. and ... syntaxRamkumar Ramachandra, Apr 21, 2013
  5. 4/7 git-log.txt: order OPTIONS properly; move <since>..<until>Ramkumar Ramachandra, Apr 21, 2013
  6. 5/7 git-log.txt: generalize <since>..<until>Ramkumar Ramachandra, Apr 21, 2013
  7. Junio C HamanoApr 21, 2013
  8. 6/7 git-log.txt: rewrite note on why "--" may be requiredRamkumar Ramachandra, Apr 21, 2013
  9. 7/7 git-shortlog.txt: make SYNOPSIS match log, update OPTIONSRamkumar Ramachandra, Apr 21, 2013
  10. Junio C HamanoApr 21, 2013

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.