git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Documentation: git-tag '-m' implies '-a'
Date: Mon, 24 Mar 2008 15:41:54 +0100	[thread overview]
Message-ID: <47E7BDB2.3030304@dirk.my1.cc> (raw)

Described that '-a' is implied when '-m' or '-F' is present.
---
 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.4.950.ga176

             reply	other threads:[~2008-03-24 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 14:41 Dirk Süsserott [this message]
2008-03-24 19:43 ` [PATCH] Documentation: git-tag '-m' implies '-a' Jeff King
2008-03-24 20:07   ` Junio C Hamano
2008-03-25  1:38     ` Jeff King
2008-03-25 17:13       ` Dirk Süsserott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47E7BDB2.3030304@dirk.my1.cc \
    --to=newsletter@dirk.my1.cc \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).