| blob | c6607eac5ede664276b4b411af6b8712e7b8b86b |
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 }
129 }
133 }
135 /* Block element titles. */
143 }
146 }
150 }
153 }
156 }
162 }
168 }
176 }
181 }
185 }
189 }
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
193 }
202 }
206 }
211 }
217 dl {
220 }
221 dt {
226 }
229 }
233 }
236 }
239 }
242 }
245 }
248 }
255 }
259 }
263 }
264 tfoot {
266 }
269 }
272 }
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
276 }
280 }
284 }
290 }
293 }
296 }
302 }
305 }
309 }
313 }
317 }
321 }
326 }
330 }
340 }
345 }
347 div#toc {
349 }
351 div#toctitle {
358 }
363 }
367 }
371 }
375 }
376 /* Overrides for manpage documents */
377 h1 {
382 }
383 h2 {
385 }
388 }
392 }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
400 }
407 }
413 }
418 }
422 }
426 }
431 }
433 /* IE6 sets dynamically generated links as visited. */
435 </style>
437 /*<![CDATA[*/
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
447 *
448 * Table Of Content generator
449 * Version: 0.4
450 *
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
453 */
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
458 // toclevels = 1..4.
468 }
470 }
476 }
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
483 // browsers).
490 }
492 }
493 }
494 }
497 }
512 }
515 },
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
524 */
534 n++;
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
547 }
548 }
552 // Process footnoterefs.
561 }
562 }
563 }
564 }
566 }
567 /*]]>*/
568 </script>
569 </head>
570 <body>
572 <h1>
573 git-describe(1) Manual Page
574 </h1>
577 <p>git-describe -
578 Show the most recent tag that is reachable from a commit
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git describe</em> [--all] [--tags] [--contains] [--abbrev=<n>] <committish>…
587 <em>git describe</em> [--all] [--tags] [--contains] [--abbrev=<n>] --dirty[=<mark>]</div>
589 </div></div>
590 </div>
594 commit. If the tag points to the commit, then only the tag is
595 shown. Otherwise, it suffixes the tag name with the number of
596 additional commits on top of the tagged object and the
597 abbreviated object name of the most recent commit.</p></div>
599 annotated tags. For more information about creating annotated tags
601 </div>
607 </dt>
608 <dd>
609 <p>
610 Committish object names to describe.
611 </p>
612 </dd>
615 </dt>
616 <dd>
617 <p>
618 Describe the working tree.
620 default) if the working tree is dirty.
621 </p>
622 </dd>
624 --all
625 </dt>
626 <dd>
627 <p>
628 Instead of using only the annotated tags, use any ref
630 any known branch, remote-tracking branch, or lightweight tag.
631 </p>
632 </dd>
634 --tags
635 </dt>
636 <dd>
637 <p>
638 Instead of using only the annotated tags, use any tag
640 a lightweight (non-annotated) tag.
641 </p>
642 </dd>
644 --contains
645 </dt>
646 <dd>
647 <p>
648 Instead of finding the tag that predates the commit, find
649 the tag that comes after the commit, and thus contains it.
650 Automatically implies --tags.
651 </p>
652 </dd>
655 </dt>
656 <dd>
657 <p>
658 Instead of using the default 7 hexadecimal digits as the
661 will suppress long format, only showing the closest tag.
662 </p>
663 </dd>
666 </dt>
667 <dd>
668 <p>
669 Instead of considering only the 10 most recent tags as
670 candidates to describe the input committish consider
672 slightly longer but may produce a more accurate result.
674 </p>
675 </dd>
677 --exact-match
678 </dt>
679 <dd>
680 <p>
681 Only output exact matches (a tag directly references the
682 supplied commit). This is a synonym for --candidates=0.
683 </p>
684 </dd>
686 --debug
687 </dt>
688 <dd>
689 <p>
690 Verbosely display information about the searching strategy
691 being employed to standard error. The tag name will still
692 be printed to standard out.
693 </p>
694 </dd>
696 --long
697 </dt>
698 <dd>
699 <p>
700 Always output the long format (the tag, the number of commits
701 and the abbreviated commit name) even when it matches a tag.
702 This is useful when you want to see parts of the commit object name
703 in "describe" output, even when the commit in question happens to be
704 a tagged version. Instead of just emitting the tag name, it will
706 that points at object deadbee….).
707 </p>
708 </dd>
711 </dt>
712 <dd>
713 <p>
714 Only consider tags matching the given pattern (can be used to avoid
715 leaking private tags made from the repository).
716 </p>
717 </dd>
719 --always
720 </dt>
721 <dd>
722 <p>
723 Show uniquely abbreviated commit object as fallback.
724 </p>
725 </dd>
726 </dl></div>
727 </div>
733 <pre><tt>[torvalds@g5 git]$ git describe parent
735 </div></div>
737 but since it has a few commits on top of that,
738 describe has added the number of additional commits ("14") and
739 an abbreviated object name for the commit itself ("2414721")
740 at the end.</p></div>
742 of commits which would be displayed by "git log v1.0.4..parent".
746 a software depending on the SCM the software is managed with. This is useful
747 in an environment where people may use different SCMs.</p></div>
748 <div class="paragraph"><p>Doing a <em>git describe</em> on a tag-name will just show the tag name:</p></div>
753 </div></div>
755 the output shows the reference path as well:</p></div>
760 </div></div>
765 </div></div>
767 closest tagname without any suffix:</p></div>
772 </div></div>
774 longer than what Linus saw above when he ran these commands, as your
775 git repository may have new commits whose object names begin with
777 be sufficient to disambiguate these commits.</p></div>
778 </div>
781 <div class="paragraph"><p>For each committish supplied, <em>git describe</em> will first look for
782 a tag which tags exactly that commit. Annotated tags will always
783 be preferred over lightweight tags, and tags with newer dates will
784 always be preferred over tags with older dates. If an exact match
785 is found, its name will be output and searching will stop.</p></div>
787 through the commit history to locate an ancestor commit which
788 has been tagged. The ancestor’s tag will be output along with an
791 has the fewest commits different from the input committish will be
792 selected and output. Here fewest commits different is defined as
794 will be the smallest number of commits possible.</p></div>
795 </div>
799 </div>
800 </div>
805 </div>
806 </div>
807 </body>
808 </html>