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

[PATCH] git-tag.txt: <commit> for --contains is optional

From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Date
Feb 4, 2014, 02:56 UTC
Message-ID
<1391482586-26444-1-git-send-email-pclouds@gmail.com>

This goes far back to e84fb2f (branch --contains: default to HEAD - 2008-07-08) where the same parsing code is shared with builtin/tag.c. git-branch.txt correctly states that <commit> for --contains is optional while git-tag.txt does not. Correct it.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
 Documentation/git-tag.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index c418c44..404257d 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -103,8 +103,9 @@ OPTIONS
 +
 This option is only applicable when listing tags without annotation lines.
 
---contains <commit>::
-	Only list tags which contain the specified commit.
+--contains [<commit>]::
+	Only list tags which contain the specified commit (HEAD if not
+	specified).
 
 --points-at <object>::
 	Only list tags of the given object.
-- 
1.8.5.2.240.g8478abd
Next: Junio C Hamano
Message 1 of 2 in “git-tag.txt: <commit> for --contains is optional”
  1. git-tag.txt: <commit> for --contains is optionalNguyễn Thái Ngọc Duy, Feb 4, 2014
  2. Junio C HamanoFeb 4, 2014

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.