| blob | 4717ec7e6bd2ebf1c8aeef06b805f9f88749c091 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-tag(1) Manual Page
407 </h1>
410 <p>git-tag -
411 Create, list, delete or verify a tag object signed with GPG
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git tag</em> [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]
424 </div></div>
425 </div>
428 <div class="paragraph"><p>Add a tag reference in <tt>.git/refs/tags/</tt>, unless <tt>-d/-l/-v</tt> is given
429 to delete, list or verify tags.</p></div>
430 <div class="paragraph"><p>Unless <tt>-f</tt> is given, the tag to be created must not yet exist in the
432 <div class="paragraph"><p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command
434 <tt>-m <msg></tt> or <tt>-F <file></tt> is given, an editor is started for the user to type
435 in the tag message.</p></div>
436 <div class="paragraph"><p>If <tt>-m <msg></tt> or <tt>-F <file></tt> is given and <tt>-a</tt>, <tt>-s</tt>, and <tt>-u <key-id></tt>
438 <div class="paragraph"><p>Otherwise just a tag reference for the SHA1 object name of the commit object is
439 created (i.e. a lightweight tag).</p></div>
442 committer identity for the current user is used to find the
443 GnuPG key for signing.</p></div>
444 </div>
449 -a
450 </dt>
451 <dd>
452 <p>
453 Make an unsigned, annotated tag object
454 </p>
455 </dd>
457 -s
458 </dt>
459 <dd>
460 <p>
461 Make a GPG-signed tag, using the default e-mail address’s key
462 </p>
463 </dd>
466 </dt>
467 <dd>
468 <p>
469 Make a GPG-signed tag, using the given key
470 </p>
471 </dd>
473 -f
474 </dt>
476 --force
477 </dt>
478 <dd>
479 <p>
480 Replace an existing tag with the given name (instead of failing)
481 </p>
482 </dd>
484 -d
485 </dt>
486 <dd>
487 <p>
488 Delete existing tags with the given names.
489 </p>
490 </dd>
492 -v
493 </dt>
494 <dd>
495 <p>
496 Verify the gpg signature of the given tag names.
497 </p>
498 </dd>
501 </dt>
502 <dd>
503 <p>
505 are printed when using -l.
506 The default is not to print any annotation lines.
508 If the tag is not annotated, the commit message is displayed instead.
509 </p>
510 </dd>
513 </dt>
514 <dd>
515 <p>
516 List tags with names that match the given pattern (or all if no
517 pattern is given). Running "git tag" without arguments also
518 lists all tags. The pattern is a shell wildcard (i.e., matched
519 using fnmatch(3)). Multiple patterns may be given; if any of
520 them matches, the tag is shown.
521 </p>
522 </dd>
525 </dt>
526 <dd>
527 <p>
528 Only list tags which contain the specified commit.
529 </p>
530 </dd>
533 </dt>
534 <dd>
535 <p>
536 Use the given tag message (instead of prompting).
538 concatenated as separate paragraphs.
540 is given.
541 </p>
542 </dd>
545 </dt>
546 <dd>
547 <p>
549 read the message from the standard input.
551 is given.
552 </p>
553 </dd>
556 </dt>
557 <dd>
558 <p>
559 The name of the tag to create, delete, or describe.
560 The new tag name must pass all checks defined by
562 may restrict the characters allowed in a tag name.
563 </p>
564 </dd>
565 </dl></div>
566 </div>
569 <div class="paragraph"><p>By default, <em>git tag</em> in sign-with-default mode (-s) will use your
570 committer identity (of the form "Your Name <<a href="mailto:your@email.address">your@email.address</a>>") to
571 find a key. If you want to use a different default key, you can specify
572 it in the repository configuration as follows:</p></div>
575 <pre><tt>[user]
577 </div></div>
578 </div>
583 want to re-tag?</p></div>
587 your repository directly), then others will have already seen
588 the old tag. In that case you can do one of two things:</p></div>
590 <li>
591 <p>
592 The sane thing.
593 Just admit you screwed up, and use a different name. Others have
594 already seen one tag-name, and if you keep the same name, you
595 may be in the situation that two people both have "version X",
597 and be done with it.
598 </p>
599 </li>
600 <li>
601 <p>
602 The insane thing.
605 again, as if you hadn’t already published the old one.
606 </p>
607 </li>
608 </ol></div>
609 <div class="paragraph"><p>However, Git does <strong>not</strong> (and it should not) change tags behind
610 users back. So if somebody already got the old tag, doing a
612 one.</p></div>
614 the tag for them by updating your own one. This is a big
615 security issue, in that people MUST be able to trust their
616 tag-names. If you really want to do the insane thing, you need
617 to just fess up to it, and tell people that you messed up. You
618 can do that by making a very public announcement saying:</p></div>
621 <pre><tt>Ok, I messed up, and I pushed out an earlier version tagged as X. I
622 then fixed something, and retagged the *fixed* tree as X again.
624 If you got the wrong tag, and want the new one, please delete
625 the old one and fetch the new one by doing:
627 git tag -d X
628 git fetch origin tag X
630 to get my updated tag.
632 You can test which tag you have by doing
634 git rev-parse X
636 which should return 0123456789abcdef.. if you have the new version.
638 Sorry for the inconvenience.</tt></pre>
639 </div></div>
640 <div class="paragraph"><p>Does this seem a bit complicated? It <strong>should</strong> be. There is no
641 way that it would be correct to just "fix" it automatically.
642 People need to know that their tags might have been changed.</p></div>
647 layout). You usually want the tags from the other end.</p></div>
649 one-shot merge from somebody else, you typically do not want to
650 get tags from there. This happens more often for people near
651 the toplevel but not limited to them. Mere mortals when pulling
652 from each other do not necessarily want to automatically get
653 private anchor point tags from the other person.</p></div>
655 two pieces of information: a repo URL and a branch name; this
657 command line:</p></div>
660 <pre><tt>Linus, please pull from
662 git://git..../proj.git master
664 to get the following updates...</tt></pre>
665 </div></div>
670 </div></div>
674 largely means there is no inherent "upstream" or
675 "downstream" in the system. On the face of it, the above
676 example might seem to indicate that the tag namespace is owned
677 by the upper echelon of people and that tags only flow downwards, but
678 that is not the case. It only shows that the usage pattern
679 determines who are interested in whose tags.</p></div>
681 the boundary between one circle of people (e.g. "people who are
682 primarily interested in the networking part of the kernel") who may
683 have their own set of tags (e.g. "this is the third release
684 candidate from the networking group to be proposed for general
685 consumption with 2.6.21 release") to another circle of people
686 (e.g. "people who integrate various subsystem improvements").
687 The latter are usually not interested in the detailed tags used
688 internally in the former group (that is what "internal" means).
689 That is why it is desirable not to follow tags automatically in
690 this case.</p></div>
692 exchange the tags internal to their group, but in that workflow
693 they are most likely tracking each other’s progress by
694 having remote-tracking branches. Again, the heuristic to automatically
695 follow such tags is a good thing.</p></div>
698 to add tags for major releases of your work, it is useful to be able
699 to specify the date to embed inside of the tag object; such data in
700 the tag object affects, for example, the ordering of tags in the
701 gitweb interface.</p></div>
703 variable GIT_COMMITTER_DATE (see the later discussion of possible
709 </div></div>
710 </div>
714 support the following date formats:</p></div>
717 Git internal format
718 </dt>
719 <dd>
720 <p>
725 </p>
726 </dd>
728 RFC 2822
729 </dt>
730 <dd>
731 <p>
732 The standard email format as described by RFC 2822, for example
734 </p>
735 </dd>
737 ISO 8601
738 </dt>
739 <dd>
740 <p>
741 Time and date specified by the ISO 8601 standard, for example
744 </p>
746 <table><tr>
749 </td>
752 </tr></table>
753 </div>
754 </dd>
755 </dl></div>
756 </div>
759 <div class="paragraph"><p><a href="git-check-ref-format.html">git-check-ref-format(1)</a>.</p></div>
760 </div>
764 </div>
768 </div>
769 </div>
770 </body>
771 </html>