path: root/Documentation/git-tag.txt
AgeCommit message (Collapse)Author
2008-01-07Documentation: rename gitlink macro to linkgitDan McGee
Between AsciiDoc 8.2.2 and 8.2.3, the following change was made to the stock Asciidoc configuration: @@ -149,7 +153,10 @@ # Inline macros. # Backslash prefix required for escape processing. # (?s) re flag for line spanning. -(?su)[\\]?(?P<name>\w(\w|-)*?):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])= + +# Explicit so they can be nested. +(?su)[\\]?(?P<name>(http|https|ftp|file|mailto|callto|image|link)):(?P<target>\S*?)(\[(?P<attrlist>.*?)\])= + # Anchor: [[[id]]]. Bibliographic anchor. (?su)[\\]?\[\[\[(?P<attrlist>[\w][\w-]*?)\]\]\]=anchor3 # Anchor: [[id,xreflabel]] This default regex now matches explicit values, and unfortunately in this case gitlink was being matched by just 'link', causing the wrong inline macro template to be applied. By renaming the macro, we can avoid being matched by the wrong regex. Signed-off-by: Dan McGee <> Signed-off-by: Junio C Hamano <>
2007-11-23builtin-tag: accept and process multiple -m just like git-commitJunio C Hamano
Signed-off-by: Junio C Hamano <>
2007-10-16Documentation/git-tag.txt: Document how to backdate tagsMichael Olson
Added a new section beneath "On Automatic following" called "On Backdating Tags". This includes an explanation of when to use this method, a brief explanation of the kind of date that can be used in GIT_AUTHOR_DATE, and an example invocation of git-tag using a custom setting of GIT_AUTHOR_DATE. [sp: Corrected s/you/your/, noticed by Jeff King] Signed-off-by: Michael W. Olson <> Signed-off-by: Shawn O. Pearce <>
2007-10-16Fix some typos, punctuation, missing words, minor markup.Ralf Wildenhues
Signed-off-by: Lars Hjemli <> Signed-off-by: Shawn O. Pearce <>
2007-08-27git-tag(1): Remove duplicate textJari Aalto
Options -d, -l, -v have already been explained in OPTIONS below. Signed-off-by: Jari Aalto <> Signed-off-by: Junio C Hamano <>
2007-07-20Make git tag a builtin.Carlos Rica
This replaces the script "" with "builtin-tag.c". The existing test suite for "git tag" guarantees the compatibility with the features provided by the script version. There are some minor changes in the behaviour of "git tag" here: "git tag -v" now can get more than one tag to verify, like "git tag -d" does, "git tag" with no arguments prints all tags, more like "git branch" does, and "git tag -n" also prints all tags with annotations (without needing -l). Tests and documentation were also updated to reflect these changes. The program is currently calling the script "git verify-tag" for verify. This can be changed porting it to C and calling its functions directly from builtin-tag.c. Signed-off-by: Carlos Rica <> Signed-off-by: Junio C Hamano <>
2007-06-03Teach git-tag about showing tag annotations.Matthijs Melchior
The <pattern> for -l is now a shell pattern, not a list of grep parameters. Option -l may be repeated with another <pattern>. The new -n [<num>] option specifies how many lines from the annotation are to be printed. Not specifieing -n or -n 0 will just produce the tag names Just -n or -n 1 will show the first line of the annotation on the tag line. Other valuse for -n will show that number of lines from the annotation. The exit code used to indicate if any tag was found. This is changed due to a different implementation. A good way to test a tag for existence is to use: git show-ref --quiet --verify refs/tags/$TAGNAME Signed-off-by: Matthijs Melchior <> Signed-off-by: Junio C Hamano <>
2007-05-04git-tag(1): -v option is a subcommand; fix code blockJonas Fonseca
When the -v is passed, git-tag will exit after it is processed like it does with the -d and -l options. Additionally, missing code block caused wrong rendering of an option example. Signed-off-by: Jonas Fonseca <> Signed-off-by: Junio C Hamano <>
2007-02-12Add discussion section to git-tag documentation.Junio C Hamano
Signed-off-by: Junio C Hamano <>
2007-01-27Allow the tag signing key to be specified in the config fileAndy Parkins
I did this: $ git tag -s test-sign gpg: skipped "Andy Parkins <>": secret key not available gpg: signing failed: secret key not available failed to sign the tag with GPG. The problem is that I have used the comment field in my key's UID definition. $ gpg --list-keys andy pub 1024D/4F712F6D 2003-08-14 uid Andy Parkins (Google) <> So when git-tag looks for "Andy Parkins <>"; obviously it's not going to be found. There shouldn't be a requirement that I use the same form of my name in my git repository and my gpg key - I might want to be formal (Andrew) in my gpg key and informal (Andy) in the repository. Further I might have multiple keys in my keyring, and might want to use one that doesn't match up with the address I use in commit messages. This patch adds a configuration entry "user.signingkey" which, if present, will be passed to the "-u" switch for gpg, allowing the tag signing key to be overridden. If the entry is not present, the fallback is the original method, which means existing behaviour will continue untouched. Signed-off-by: Andy Parkins <> Signed-off-by: Junio C Hamano <>
2007-01-21git-tag -d: allow deleting multiple tags at once.Junio C Hamano
Signed-off-by: Junio C Hamano <>
2007-01-17Documentation/git-tag: the command can be used to also verify a tag.Junio C Hamano
Signed-off-by: Junio C Hamano <>
2007-01-03git-tag: add flag to verify a tagSanti Béjar
This way "git tag -v $tag" is the UI for git-verify-tag. Signed-off-by: Santi Béjar <> Signed-off-by: Junio C Hamano <>
2006-12-22git-tag: support -F <file> optionJohannes Schindelin
This imitates the behaviour of git-commit. Noticed by Han-Wen Nienhuys. Signed-off-by: Johannes Schindelin <> Signed-off-by: Junio C Hamano <>
2006-03-09Fix some inconsistencies in the docsFredrik Kuivinen
Signed-off-by: Fredrik Kuivinen <> Signed-off-by: Junio C Hamano <>
2006-02-17git-tag: -l to list tags (usability).Junio C Hamano
git-tag -l lists all tags, and git-tag -l <pattern> filters the result with <pattern>. Signed-off-by: Junio C Hamano <>
2005-12-08Documentation/git-tag.txt: Fix the order of sections (DESCRIPTION should ↵Nikolai Weibull
come before OPTIONS). Signed-off-by: Nikolai Weibull <> Signed-off-by: Junio C Hamano <>
2005-12-02documentation: git-tagNo name
[jc: light edit applied on top of the original] Signed-off-by: Junio C Hamano <>
2005-11-08git-tag -d <tag>: delete tag <tag>Kai Ruemmler
This adds option '-d' to and documents it. Signed-off-by: Kai Ruemmler <> Signed-off-by: Junio C Hamano <>
2005-10-10Merge branch 'fixes'Junio C Hamano
with minor hand resolving on git-tag. Signed-off-by: Junio C Hamano <>
2005-10-10git-tag: update usage string and documentation.Junio C Hamano
Signed-off-by: Junio C Hamano <>
2005-10-06Allow "-u" flag to tag signingLinus Torvalds
The current "git tag -s" thing always uses the tagger name as the signing user key, which is very irritating, since my key is under my email address, but the tagger key obviously contains the actual machine name too. Now, I could just use "GIT_COMMITTER_EMAIL" and force it to be my real email, but I actually think that it's nice to see which machine I use for my work. So rather than force my tagger ID to have to match the gpg key name, just support the "-u" flag to "git tag" instead. It implicitly enables signing, since it doesn't make any sense without it. Thus: git tag -u <gpg-key-name> <tag-name> [<tagged-object>] will use the named gpg key for signing. Signed-off-by: Linus Torvalds <> Signed-off-by: Junio C Hamano <>
2005-09-20[PATCH] Documentation: Update all files to use the new gitlink: macroSergey Vlasov
The replacement was performed automatically by these commands: perl -pi -e 's/link:(git.+)\.html\[\1\]/gitlink:$1\[1\]/g' \ README Documentation/*.txt perl -pi -e 's/link:git\.html\[git\]/gitlink:git\[7\]/g' \ README Documentation/*.txt Signed-off-by: Sergey Vlasov <> Signed-off-by: Junio C Hamano <>
2005-09-08Big tool rename.Junio C Hamano
As promised, this is the "big tool rename" patch. The primary differences since 0.99.6 are: (1) git-*-script are no more. The commands installed do not have any such suffix so users do not have to remember if something is implemented as a shell script or not. (2) Many command names with 'cache' in them are renamed with 'index' if that is what they mean. There are backward compatibility symblic links so that you and Porcelains can keep using the old names, but the backward compatibility support is expected to be removed in the near future. Signed-off-by: Junio C Hamano <>