| blob | 6d64d00d76fa4c200fca6abcb80b19367509e0f1 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-tag(1) Manual Page
313 </h1>
316 <p>git-tag -
317 Create, list, delete or verify a tag object signed with GPG
318 </p>
319 </div>
320 </div>
324 <div class="content"><em>git tag</em> [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>]
329 </div>
335 <div class="para"><p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command
337 <tt>-m <msg></tt> or <tt>-F <file></tt> is given, an editor is started for the user to type
338 in the tag message.</p></div>
339 <div class="para"><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>
342 written (i.e. a lightweight tag).</p></div>
345 committer identity for the current user is used to find the
346 GnuPG key for signing.</p></div>
347 </div>
351 <dt>
352 -a
353 </dt>
354 <dd>
355 <p>
356 Make an unsigned, annotated tag object
357 </p>
358 </dd>
359 <dt>
360 -s
361 </dt>
362 <dd>
363 <p>
364 Make a GPG-signed tag, using the default e-mail address's key
365 </p>
366 </dd>
367 <dt>
369 </dt>
370 <dd>
371 <p>
372 Make a GPG-signed tag, using the given key
373 </p>
374 </dd>
375 <dt>
376 -f
377 </dt>
378 <dd>
379 <p>
380 Replace an existing tag with the given name (instead of failing)
381 </p>
382 </dd>
383 <dt>
384 -d
385 </dt>
386 <dd>
387 <p>
388 Delete existing tags with the given names.
389 </p>
390 </dd>
391 <dt>
392 -v
393 </dt>
394 <dd>
395 <p>
396 Verify the gpg signature of the given tag names.
397 </p>
398 </dd>
399 <dt>
401 </dt>
402 <dd>
403 <p>
405 are printed when using -l.
406 The default is not to print any annotation lines.
408 If the tag is not annotated, the commit message is displayed instead.
409 </p>
410 </dd>
411 <dt>
413 </dt>
414 <dd>
415 <p>
416 List tags with names that match the given pattern (or all if no pattern is given).
417 Typing "git tag" without arguments, also lists all tags.
418 </p>
419 </dd>
420 <dt>
422 </dt>
423 <dd>
424 <p>
425 Only list tags which contain the specified commit.
426 </p>
427 </dd>
428 <dt>
430 </dt>
431 <dd>
432 <p>
433 Use the given tag message (instead of prompting).
435 concatenated as separate paragraphs.
437 is given.
438 </p>
439 </dd>
440 <dt>
442 </dt>
443 <dd>
444 <p>
446 read the message from the standard input.
448 is given.
449 </p>
450 </dd>
451 </dl></div>
452 </div>
456 committer identity (of the form "Your Name <your@email.address>") to
457 find a key. If you want to use a different default key, you can specify
458 it in the repository configuration as follows:</p></div>
461 <pre><tt>[user]
463 </div></div>
464 </div>
469 want to re-tag?</p></div>
471 replace the old one. And you're done.</p></div>
473 your repository directly), then others will have already seen
474 the old tag. In that case you can do one of two things:</p></div>
476 <li>
477 <p>
478 The sane thing.
479 Just admit you screwed up, and use a different name. Others have
480 already seen one tag-name, and if you keep the same name, you
481 may be in the situation that two people both have "version X",
483 and be done with it.
484 </p>
485 </li>
486 <li>
487 <p>
488 The insane thing.
491 again, as if you hadn't already published the old one.
492 </p>
493 </li>
494 </ol></div>
495 <div class="para"><p>However, Git does <strong>not</strong> (and it should not) change tags behind
496 users back. So if somebody already got the old tag, doing a
498 one.</p></div>
500 the tag for them by updating your own one. This is a big
501 security issue, in that people MUST be able to trust their
502 tag-names. If you really want to do the insane thing, you need
503 to just fess up to it, and tell people that you messed up. You
504 can do that by making a very public announcement saying:</p></div>
507 <pre><tt>Ok, I messed up, and I pushed out an earlier version tagged as X. I
508 then fixed something, and retagged the *fixed* tree as X again.
510 If you got the wrong tag, and want the new one, please delete
511 the old one and fetch the new one by doing:
513 git tag -d X
514 git fetch origin tag X
516 to get my updated tag.
518 You can test which tag you have by doing
520 git rev-parse X
522 which should return 0123456789abcdef.. if you have the new version.
524 Sorry for inconvenience.</tt></pre>
525 </div></div>
526 <div class="para"><p>Does this seem a bit complicated? It <strong>should</strong> be. There is no
527 way that it would be correct to just "fix" it behind peoples
528 backs. People need to know that their tags might have been
529 changed.</p></div>
534 layout). You usually want the tags from the other end.</p></div>
536 one-shot merge from somebody else, you typically do not want to
537 get tags from there. This happens more often for people near
538 the toplevel but not limited to them. Mere mortals when pulling
539 from each other do not necessarily want to automatically get
540 private anchor point tags from the other person.</p></div>
542 repo URL and branch name alone. This is designed to be easily
546 <pre><tt>Linus, please pull from
548 git://git..../proj.git master
550 to get the following updates...</tt></pre>
551 </div></div>
556 </div></div>
558 tags.</p></div>
560 distributed largely means there is no inherent "upstream" or
561 "downstream" in the system. On the face of it, the above
562 example might seem to indicate that the tag namespace is owned
563 by upper echelon of people and tags only flow downwards, but
564 that is not the case. It only shows that the usage pattern
565 determines who are interested in whose tags.</p></div>
567 the boundary between one circle of people (e.g. "people who are
568 primarily interested in the networking part of the kernel") who may
569 have their own set of tags (e.g. "this is the third release
570 candidate from the networking group to be proposed for general
571 consumption with 2.6.21 release") to another circle of people
572 (e.g. "people who integrate various subsystem improvements").
573 The latter are usually not interested in the detailed tags used
574 internally in the former group (that is what "internal" means).
575 That is why it is desirable not to follow tags automatically in
576 this case.</p></div>
578 exchange the tags internal to their group, but in that workflow
579 they are most likely tracking with each other's progress by
580 having tracking branches. Again, the heuristic to automatically
581 follow such tags is a good thing.</p></div>
584 to add tags for major releases of your work, it is useful to be able
585 to specify the date to embed inside of the tag object. The data in
586 the tag object affects, for example, the ordering of tags in the
587 gitweb interface.</p></div>
589 variable GIT_COMMITTER_DATE to one or more of the date and time. The
590 date and time can be specified in a number of ways; the most common
596 </div></div>
597 </div>
602 </div>
605 <div class="para"><p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p></div>
606 </div>
610 </div>
614 </div>
615 </div>
616 </body>
617 </html>