Split up the --[no-]merged documentation into documentation that
documents each option independently. This is in line with how "branch"
and "for-each-ref" are documented, and makes subsequent changes to
discuss the limits & caveats of each option easier to read.

Signed-off-by: Ævar Arnfjörð Bjarmason <ava...@gmail.com>
---
 Documentation/git-tag.txt | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index 33f18ea5fb..68b0ab2410 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -124,10 +124,13 @@ This option is only applicable when listing tags without 
annotation lines.
        Only list tags which contain the specified commit (HEAD if not
        specified).
 
---[no-]merged [<commit>]::
-       Only list tags whose tips are reachable, or not reachable
-       if `--no-merged` is used, from the specified commit (`HEAD`
-       if not specified).
+--merged [<commit>]::
+       Only list tags whose tips are reachable from the specified commit
+       (`HEAD` if not specified).
+
+--no-merged [<commit>]::
+       Only list tags whose tips are not reachable from the specified
+       commit (`HEAD` if not specified).
 
 --points-at <object>::
        Only list tags of the given object.
-- 
2.11.0

Reply via email to