{"thread":{"id":"12842","subject":"[PATCH] Documentation/git-tag.txt: Clarify tagging of objects","startedAt":"2008-03-24T15:11:45Z","lastAt":"2008-03-24T18:16:26Z","messageCount":2,"participants":["Pieter de Bie","Carlos Rica"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"72903","messageId":"1206371505-7698-1-git-send-email-pdebie@ai.rug.nl","threadId":"12842","inReplyTo":null,"subject":"[PATCH] Documentation/git-tag.txt: Clarify tagging of objects","fromName":"Pieter de Bie","fromEmail":"pdebie@ai.rug.nl","sentAt":"2008-03-24T15:11:45Z","receivedAt":"2008-03-24T15:11:45Z","isPatch":true,"sender":{"key":"pdebie@ai.rug.nl","avatar":null},"body":"Change the synopsis and description of git-tag to reflect that any\nobject can be tagged, not just a committish.\n---\nThis surprised me, so I guess the documentation deserves some attention.\nI'm only able to build the HTML documentation, so I hope this looks correct\nin manpages too.\n\n-  Pieter\n\n\n Documentation/git-tag.txt |   11 ++++++++---\n 1 files changed, 8 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt\nindex b62a3d1..9702f2f 100644\n--- a/Documentation/git-tag.txt\n+++ b/Documentation/git-tag.txt\n@@ -9,7 +9,7 @@ git-tag - Create, list, delete or verify a tag object signed with GPG\n SYNOPSIS\n --------\n [verse]\n-'git-tag' [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]  <name> [<head>]\n+'git-tag' [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]  <name> [<object>]\n 'git-tag' -d <name>...\n 'git-tag' [-n [<num>]] -l [<pattern>]\n 'git-tag' -v <name>...\n@@ -18,6 +18,11 @@ DESCRIPTION\n -----------\n Adds a 'tag' reference in `.git/refs/tags/`\n \n+If `<object>` is given, the given object will be tagged. While\n+this usually is a committish, other objects may be tagged\n+as well. If `<object>` is not given, the current HEAD will be\n+tagged.\n+\n Unless `-f` is given, the tag must not yet exist in\n `.git/refs/tags/` directory.\n \n@@ -26,8 +31,8 @@ creates a 'tag' object, and requires the tag message.  Unless\n `-m <msg>` or `-F <file>` is given, an editor is started for the user to type\n in the tag message.\n \n-Otherwise just the SHA1 object name of the commit object is\n-written (i.e. a lightweight tag).\n+Otherwise just the SHA1 object name of the object is written\n+(i.e. a lightweight tag).\n \n A GnuPG signed tag object will be created when `-s` or `-u\n <key-id>` is used.  When `-u <key-id>` is not used, the\n-- \n1.5.4.4.594.g91c25\n"},{"id":"72924","messageId":"1b46aba20803241116k20072dc8wdb70e6de90ed25aa@mail.gmail.com","threadId":"12842","inReplyTo":"1206371505-7698-1-git-send-email-pdebie@ai.rug.nl","subject":"Re: [PATCH] Documentation/git-tag.txt: Clarify tagging of objects","fromName":"Carlos Rica","fromEmail":"jasampler@gmail.com","sentAt":"2008-03-24T18:16:26Z","receivedAt":"2008-03-24T18:16:26Z","isPatch":true,"sender":{"key":"jasampler@gmail.com","avatar":null},"body":"On Mon, Mar 24, 2008 at 4:11 PM, Pieter de Bie <pdebie@ai.rug.nl> wrote:\n>  -'git-tag' [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]  <name> [<head>]\n>  +'git-tag' [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]  <name> [<object>]\n\nNote that you need to change also the corresponding string inside\nbuiltin-tag.c , the lines printed when you run \"git tag -h\".\n\n--\nCarlos\n"}]}