tag doc: reword --[no-]merged to talk about commits, not tips
Change the wording for the --merged and --no-merged options to talk about "commits" instead of "tips". This phrasing was copied from the "branch" documentation in commit 5242860f54 ("tag.c: implement '--merged' and '--no-merged' options", 2015-09-10). Talking about the "tip" is branch nomenclature, not something usually associated with tags. This phrasing might lead the reader to believe that these options might find tags pointing to trees or blobs, let's instead be explicit and only talk about commits. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ævar Arnfjörð Bjarmason committed
Mar 21, 2017 at 12:58 UTC
8881d35cace41604dba72c1b6b5ab5a59e0c2b94
1 file changed
+3
-3
Documentation/git-tag.txt
+3
-3
@@ -125,11 +125,11 @@ This option is only applicable when listing tags without annotation lines.
125
specified).
126
127
--merged [<commit>]::
128
- Only list tags whose tips are reachable from the specified commit
129
- (`HEAD` if not specified).
128
+ Only list tags whose commits are reachable from the specified
129
+ commit (`HEAD` if not specified).
130
131
--no-merged [<commit>]::
132
- Only list tags whose tips are not reachable from the specified
132
+ Only list tags whose commits are not reachable from the specified
133
commit (`HEAD` if not specified).
134
135
--points-at <object>::