| blob | 367b2aff38acd8c4081542820bc8d82a39ca446a |
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>
431 <div class="paragraph"><p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command
433 <tt>-m <msg></tt> or <tt>-F <file></tt> is given, an editor is started for the user to type
434 in the tag message.</p></div>
435 <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 written (i.e. a lightweight tag).</p></div>
441 committer identity for the current user is used to find the
442 GnuPG key for signing.</p></div>
443 </div>
448 -a
449 </dt>
450 <dd>
451 <p>
452 Make an unsigned, annotated tag object
453 </p>
454 </dd>
456 -s
457 </dt>
458 <dd>
459 <p>
460 Make a GPG-signed tag, using the default e-mail address’s key
461 </p>
462 </dd>
465 </dt>
466 <dd>
467 <p>
468 Make a GPG-signed tag, using the given key
469 </p>
470 </dd>
472 -f
473 </dt>
475 --force
476 </dt>
477 <dd>
478 <p>
479 Replace an existing tag with the given name (instead of failing)
480 </p>
481 </dd>
483 -d
484 </dt>
485 <dd>
486 <p>
487 Delete existing tags with the given names.
488 </p>
489 </dd>
491 -v
492 </dt>
493 <dd>
494 <p>
495 Verify the gpg signature of the given tag names.
496 </p>
497 </dd>
500 </dt>
501 <dd>
502 <p>
504 are printed when using -l.
505 The default is not to print any annotation lines.
507 If the tag is not annotated, the commit message is displayed instead.
508 </p>
509 </dd>
512 </dt>
513 <dd>
514 <p>
515 List tags with names that match the given pattern (or all if no pattern is given).
516 Typing "git tag" without arguments, also lists all tags.
517 </p>
518 </dd>
521 </dt>
522 <dd>
523 <p>
524 Only list tags which contain the specified commit.
525 </p>
526 </dd>
529 </dt>
530 <dd>
531 <p>
532 Use the given tag message (instead of prompting).
534 concatenated as separate paragraphs.
536 is given.
537 </p>
538 </dd>
541 </dt>
542 <dd>
543 <p>
545 read the message from the standard input.
547 is given.
548 </p>
549 </dd>
552 </dt>
553 <dd>
554 <p>
555 The name of the tag to create, delete, or describe.
556 The new tag name must pass all checks defined by
558 may restrict the characters allowed in a tag name.
559 </p>
560 </dd>
561 </dl></div>
562 </div>
565 <div class="paragraph"><p>By default, <em>git tag</em> in sign-with-default mode (-s) will use your
566 committer identity (of the form "Your Name <<a href="mailto:your@email.address">your@email.address</a>>") to
567 find a key. If you want to use a different default key, you can specify
568 it in the repository configuration as follows:</p></div>
571 <pre><tt>[user]
573 </div></div>
574 </div>
579 want to re-tag?</p></div>
583 your repository directly), then others will have already seen
584 the old tag. In that case you can do one of two things:</p></div>
586 <li>
587 <p>
588 The sane thing.
589 Just admit you screwed up, and use a different name. Others have
590 already seen one tag-name, and if you keep the same name, you
591 may be in the situation that two people both have "version X",
593 and be done with it.
594 </p>
595 </li>
596 <li>
597 <p>
598 The insane thing.
601 again, as if you hadn’t already published the old one.
602 </p>
603 </li>
604 </ol></div>
605 <div class="paragraph"><p>However, Git does <strong>not</strong> (and it should not) change tags behind
606 users back. So if somebody already got the old tag, doing a
608 one.</p></div>
610 the tag for them by updating your own one. This is a big
611 security issue, in that people MUST be able to trust their
612 tag-names. If you really want to do the insane thing, you need
613 to just fess up to it, and tell people that you messed up. You
614 can do that by making a very public announcement saying:</p></div>
617 <pre><tt>Ok, I messed up, and I pushed out an earlier version tagged as X. I
618 then fixed something, and retagged the *fixed* tree as X again.
620 If you got the wrong tag, and want the new one, please delete
621 the old one and fetch the new one by doing:
623 git tag -d X
624 git fetch origin tag X
626 to get my updated tag.
628 You can test which tag you have by doing
630 git rev-parse X
632 which should return 0123456789abcdef.. if you have the new version.
634 Sorry for inconvenience.</tt></pre>
635 </div></div>
636 <div class="paragraph"><p>Does this seem a bit complicated? It <strong>should</strong> be. There is no
637 way that it would be correct to just "fix" it behind peoples
638 backs. People need to know that their tags might have been
639 changed.</p></div>
644 layout). You usually want the tags from the other end.</p></div>
646 one-shot merge from somebody else, you typically do not want to
647 get tags from there. This happens more often for people near
648 the toplevel but not limited to them. Mere mortals when pulling
649 from each other do not necessarily want to automatically get
650 private anchor point tags from the other person.</p></div>
652 repo URL and branch name alone. This is designed to be easily
656 <pre><tt>Linus, please pull from
658 git://git..../proj.git master
660 to get the following updates...</tt></pre>
661 </div></div>
666 </div></div>
668 tags.</p></div>
670 distributed largely means there is no inherent "upstream" or
671 "downstream" in the system. On the face of it, the above
672 example might seem to indicate that the tag namespace is owned
673 by upper echelon of people and tags only flow downwards, but
674 that is not the case. It only shows that the usage pattern
675 determines who are interested in whose tags.</p></div>
677 the boundary between one circle of people (e.g. "people who are
678 primarily interested in the networking part of the kernel") who may
679 have their own set of tags (e.g. "this is the third release
680 candidate from the networking group to be proposed for general
681 consumption with 2.6.21 release") to another circle of people
682 (e.g. "people who integrate various subsystem improvements").
683 The latter are usually not interested in the detailed tags used
684 internally in the former group (that is what "internal" means).
685 That is why it is desirable not to follow tags automatically in
686 this case.</p></div>
688 exchange the tags internal to their group, but in that workflow
689 they are most likely tracking with each other’s progress by
690 having remote-tracking branches. Again, the heuristic to automatically
691 follow such tags is a good thing.</p></div>
694 to add tags for major releases of your work, it is useful to be able
695 to specify the date to embed inside of the tag object. The data in
696 the tag object affects, for example, the ordering of tags in the
697 gitweb interface.</p></div>
699 variable GIT_COMMITTER_DATE to one or more of the date and time. The
700 date and time can be specified in a number of ways; the most common
706 </div></div>
707 </div>
710 <div class="paragraph"><p><a href="git-check-ref-format.html">git-check-ref-format(1)</a>.</p></div>
711 </div>
714 <div class="paragraph"><p>Written by Linus Torvalds <<a href="mailto:torvalds@osdl.org">torvalds@osdl.org</a>>,
715 Junio C Hamano <<a href="mailto:gitster@pobox.com">gitster@pobox.com</a>> and Chris Wright <<a href="mailto:chrisw@osdl.org">chrisw@osdl.org</a>>.</p></div>
716 </div>
719 <div class="paragraph"><p>Documentation by David Greaves, Junio C Hamano and the git-list <<a href="mailto:git@vger.kernel.org">git@vger.kernel.org</a>>.</p></div>
720 </div>
724 </div>
728 </div>
729 </div>
730 </body>
731 </html>