[PATCH] Documentation: git-tag '-m' implies '-a'

From

Jeff King <peff@peff.net>

Date

Mar 24, 2008, 19:43 UTC

Message-ID

<20080324194308.GE14002@coredump.intra.peff.net>

In-Reply-To

<47E7BDB2.3030304@dirk.my1.cc>

From: Dirk Süsserott <newsletter@dirk.my1.cc>

> Described that '-a' is implied when '-m' or '-F' is present.

Oh, I see you already took my suggestion before I made it. :)

Also, it is generally a good idea to:
  - at least cc Junio on patch submissions to make sure he sees it
  - sign off your patch (either with commit -s or format-patch -s).

Here is an unmangled version of the patch.

 Documentation/git-tag.txt |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index b62a3d1..c22fb71 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -26,6 +26,9 @@ creates a 'tag' object, and requires the tag message.  Unless
 `-m <msg>` or `-F <file>` is given, an editor is started for the user to type
 in the tag message.
 
+If `-m <msg>` or `-F <file>` is given and `-a`, `-s`, and `-u <key-id>`
+are absent, `-a` is implied.
+
 Otherwise just the SHA1 object name of the commit object is
 written (i.e. a lightweight tag).
 
@@ -68,10 +71,14 @@ OPTIONS
 	Use the given tag message (instead of prompting).
 	If multiple `-m` options are given, there values are
 	concatenated as separate paragraphs.
+	Implies `-a` if none of `-a`, `-s`, or `-u <key-id>`
+	is given.
 
 -F <file>::
 	Take the tag message from the given file.  Use '-' to
 	read the message from the standard input.
+	Implies `-a` if none of `-a`, `-s`, or `-u <key-id>`
+	is given.
 
 CONFIGURATION
 -------------

-- 
1.5.5.rc1.123.ge5f4e6