git-rev-parse.html

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
   3     "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
   4 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   5 <head>
   6 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
   7 <meta name="generator" content="AsciiDoc 10.2.0" />
   8 <title>git-rev-parse(1)</title>
   9 <style type="text/css">
  10 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
  11
  12 /* Default font. */
  13 body {
  14   font-family: Georgia,serif;
  15 }
  16
  17 /* Title font. */
  18 h1, h2, h3, h4, h5, h6,
  19 div.title, caption.title,
  20 thead, p.table.header,
  21 #toctitle,
  22 #author, #revnumber, #revdate, #revremark,
  23 #footer {
  24   font-family: Arial,Helvetica,sans-serif;
  25 }
  26
  27 body {
  28   margin: 1em 5% 1em 5%;
  29 }
  30
  31 a {
  32   color: blue;
  33   text-decoration: underline;
  34 }
  35 a:visited {
  36   color: fuchsia;
  37 }
  38
  39 em {
  40   font-style: italic;
  41   color: navy;
  42 }
  43
  44 strong {
  45   font-weight: bold;
  46   color: #083194;
  47 }
  48
  49 h1, h2, h3, h4, h5, h6 {
  50   color: #527bbd;
  51   margin-top: 1.2em;
  52   margin-bottom: 0.5em;
  53   line-height: 1.3;
  54 }
  55
  56 h1, h2, h3 {
  57   border-bottom: 2px solid silver;
  58 }
  59 h2 {
  60   padding-top: 0.5em;
  61 }
  62 h3 {
  63   float: left;
  64 }
  65 h3 + * {
  66   clear: left;
  67 }
  68 h5 {
  69   font-size: 1.0em;
  70 }
  71
  72 div.sectionbody {
  73   margin-left: 0;
  74 }
  75
  76 hr {
  77   border: 1px solid silver;
  78 }
  79
  80 p {
  81   margin-top: 0.5em;
  82   margin-bottom: 0.5em;
  83 }
  84
  85 ul, ol, li > p {
  86   margin-top: 0;
  87 }
  88 ul > li     { color: #aaa; }
  89 ul > li > * { color: black; }
  90
  91 .monospaced, code, pre {
  92   font-family: "Courier New", Courier, monospace;
  93   font-size: inherit;
  94   color: navy;
  95   padding: 0;
  96   margin: 0;
  97 }
  98 pre {
  99   white-space: pre-wrap;
 100 }
 101
 102 #author {
 103   color: #527bbd;
 104   font-weight: bold;
 105   font-size: 1.1em;
 106 }
 107 #email {
 108 }
 109 #revnumber, #revdate, #revremark {
 110 }
 111
 112 #footer {
 113   font-size: small;
 114   border-top: 2px solid silver;
 115   padding-top: 0.5em;
 116   margin-top: 4.0em;
 117 }
 118 #footer-text {
 119   float: left;
 120   padding-bottom: 0.5em;
 121 }
 122 #footer-badges {
 123   float: right;
 124   padding-bottom: 0.5em;
 125 }
 126
 127 #preamble {
 128   margin-top: 1.5em;
 129   margin-bottom: 1.5em;
 130 }
 131 div.imageblock, div.exampleblock, div.verseblock,
 132 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 133 div.admonitionblock {
 134   margin-top: 1.0em;
 135   margin-bottom: 1.5em;
 136 }
 137 div.admonitionblock {
 138   margin-top: 2.0em;
 139   margin-bottom: 2.0em;
 140   margin-right: 10%;
 141   color: #606060;
 142 }
 143
 144 div.content { /* Block element content. */
 145   padding: 0;
 146 }
 147
 148 /* Block element titles. */
 149 div.title, caption.title {
 150   color: #527bbd;
 151   font-weight: bold;
 152   text-align: left;
 153   margin-top: 1.0em;
 154   margin-bottom: 0.5em;
 155 }
 156 div.title + * {
 157   margin-top: 0;
 158 }
 159
 160 td div.title:first-child {
 161   margin-top: 0.0em;
 162 }
 163 div.content div.title:first-child {
 164   margin-top: 0.0em;
 165 }
 166 div.content + div.title {
 167   margin-top: 0.0em;
 168 }
 169
 170 div.sidebarblock > div.content {
 171   background: #ffffee;
 172   border: 1px solid #dddddd;
 173   border-left: 4px solid #f0f0f0;
 174   padding: 0.5em;
 175 }
 176
 177 div.listingblock > div.content {
 178   border: 1px solid #dddddd;
 179   border-left: 5px solid #f0f0f0;
 180   background: #f8f8f8;
 181   padding: 0.5em;
 182 }
 183
 184 div.quoteblock, div.verseblock {
 185   padding-left: 1.0em;
 186   margin-left: 1.0em;
 187   margin-right: 10%;
 188   border-left: 5px solid #f0f0f0;
 189   color: #888;
 190 }
 191
 192 div.quoteblock > div.attribution {
 193   padding-top: 0.5em;
 194   text-align: right;
 195 }
 196
 197 div.verseblock > pre.content {
 198   font-family: inherit;
 199   font-size: inherit;
 200 }
 201 div.verseblock > div.attribution {
 202   padding-top: 0.75em;
 203   text-align: left;
 204 }
 205 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
 206 div.verseblock + div.attribution {
 207   text-align: left;
 208 }
 209
 210 div.admonitionblock .icon {
 211   vertical-align: top;
 212   font-size: 1.1em;
 213   font-weight: bold;
 214   text-decoration: underline;
 215   color: #527bbd;
 216   padding-right: 0.5em;
 217 }
 218 div.admonitionblock td.content {
 219   padding-left: 0.5em;
 220   border-left: 3px solid #dddddd;
 221 }
 222
 223 div.exampleblock > div.content {
 224   border-left: 3px solid #dddddd;
 225   padding-left: 0.5em;
 226 }
 227
 228 div.imageblock div.content { padding-left: 0; }
 229 span.image img { border-style: none; vertical-align: text-bottom; }
 230 a.image:visited { color: white; }
 231
 232 dl {
 233   margin-top: 0.8em;
 234   margin-bottom: 0.8em;
 235 }
 236 dt {
 237   margin-top: 0.5em;
 238   margin-bottom: 0;
 239   font-style: normal;
 240   color: navy;
 241 }
 242 dd > *:first-child {
 243   margin-top: 0.1em;
 244 }
 245
 246 ul, ol {
 247     list-style-position: outside;
 248 }
 249 ol.arabic {
 250   list-style-type: decimal;
 251 }
 252 ol.loweralpha {
 253   list-style-type: lower-alpha;
 254 }
 255 ol.upperalpha {
 256   list-style-type: upper-alpha;
 257 }
 258 ol.lowerroman {
 259   list-style-type: lower-roman;
 260 }
 261 ol.upperroman {
 262   list-style-type: upper-roman;
 263 }
 264
 265 div.compact ul, div.compact ol,
 266 div.compact p, div.compact p,
 267 div.compact div, div.compact div {
 268   margin-top: 0.1em;
 269   margin-bottom: 0.1em;
 270 }
 271
 272 tfoot {
 273   font-weight: bold;
 274 }
 275 td > div.verse {
 276   white-space: pre;
 277 }
 278
 279 div.hdlist {
 280   margin-top: 0.8em;
 281   margin-bottom: 0.8em;
 282 }
 283 div.hdlist tr {
 284   padding-bottom: 15px;
 285 }
 286 dt.hdlist1.strong, td.hdlist1.strong {
 287   font-weight: bold;
 288 }
 289 td.hdlist1 {
 290   vertical-align: top;
 291   font-style: normal;
 292   padding-right: 0.8em;
 293   color: navy;
 294 }
 295 td.hdlist2 {
 296   vertical-align: top;
 297 }
 298 div.hdlist.compact tr {
 299   margin: 0;
 300   padding-bottom: 0;
 301 }
 302
 303 .comment {
 304   background: yellow;
 305 }
 306
 307 .footnote, .footnoteref {
 308   font-size: 0.8em;
 309 }
 310
 311 span.footnote, span.footnoteref {
 312   vertical-align: super;
 313 }
 314
 315 #footnotes {
 316   margin: 20px 0 20px 0;
 317   padding: 7px 0 0 0;
 318 }
 319
 320 #footnotes div.footnote {
 321   margin: 0 0 5px 0;
 322 }
 323
 324 #footnotes hr {
 325   border: none;
 326   border-top: 1px solid silver;
 327   height: 1px;
 328   text-align: left;
 329   margin-left: 0;
 330   width: 20%;
 331   min-width: 100px;
 332 }
 333
 334 div.colist td {
 335   padding-right: 0.5em;
 336   padding-bottom: 0.3em;
 337   vertical-align: top;
 338 }
 339 div.colist td img {
 340   margin-top: 0.3em;
 341 }
 342
 343 @media print {
 344   #footer-badges { display: none; }
 345 }
 346
 347 #toc {
 348   margin-bottom: 2.5em;
 349 }
 350
 351 #toctitle {
 352   color: #527bbd;
 353   font-size: 1.1em;
 354   font-weight: bold;
 355   margin-top: 1.0em;
 356   margin-bottom: 0.1em;
 357 }
 358
 359 div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
 360   margin-top: 0;
 361   margin-bottom: 0;
 362 }
 363 div.toclevel2 {
 364   margin-left: 2em;
 365   font-size: 0.9em;
 366 }
 367 div.toclevel3 {
 368   margin-left: 4em;
 369   font-size: 0.9em;
 370 }
 371 div.toclevel4 {
 372   margin-left: 6em;
 373   font-size: 0.9em;
 374 }
 375
 376 span.aqua { color: aqua; }
 377 span.black { color: black; }
 378 span.blue { color: blue; }
 379 span.fuchsia { color: fuchsia; }
 380 span.gray { color: gray; }
 381 span.green { color: green; }
 382 span.lime { color: lime; }
 383 span.maroon { color: maroon; }
 384 span.navy { color: navy; }
 385 span.olive { color: olive; }
 386 span.purple { color: purple; }
 387 span.red { color: red; }
 388 span.silver { color: silver; }
 389 span.teal { color: teal; }
 390 span.white { color: white; }
 391 span.yellow { color: yellow; }
 392
 393 span.aqua-background { background: aqua; }
 394 span.black-background { background: black; }
 395 span.blue-background { background: blue; }
 396 span.fuchsia-background { background: fuchsia; }
 397 span.gray-background { background: gray; }
 398 span.green-background { background: green; }
 399 span.lime-background { background: lime; }
 400 span.maroon-background { background: maroon; }
 401 span.navy-background { background: navy; }
 402 span.olive-background { background: olive; }
 403 span.purple-background { background: purple; }
 404 span.red-background { background: red; }
 405 span.silver-background { background: silver; }
 406 span.teal-background { background: teal; }
 407 span.white-background { background: white; }
 408 span.yellow-background { background: yellow; }
 409
 410 span.big { font-size: 2em; }
 411 span.small { font-size: 0.6em; }
 412
 413 span.underline { text-decoration: underline; }
 414 span.overline { text-decoration: overline; }
 415 span.line-through { text-decoration: line-through; }
 416
 417 div.unbreakable { page-break-inside: avoid; }
 418
 419
 420 /*
 421  * xhtml11 specific
 422  *
 423  * */
 424
 425 div.tableblock {
 426   margin-top: 1.0em;
 427   margin-bottom: 1.5em;
 428 }
 429 div.tableblock > table {
 430   border: 3px solid #527bbd;
 431 }
 432 thead, p.table.header {
 433   font-weight: bold;
 434   color: #527bbd;
 435 }
 436 p.table {
 437   margin-top: 0;
 438 }
 439 /* Because the table frame attribute is overridden by CSS in most browsers. */
 440 div.tableblock > table[frame="void"] {
 441   border-style: none;
 442 }
 443 div.tableblock > table[frame="hsides"] {
 444   border-left-style: none;
 445   border-right-style: none;
 446 }
 447 div.tableblock > table[frame="vsides"] {
 448   border-top-style: none;
 449   border-bottom-style: none;
 450 }
 451
 452
 453 /*
 454  * html5 specific
 455  *
 456  * */
 457
 458 table.tableblock {
 459   margin-top: 1.0em;
 460   margin-bottom: 1.5em;
 461 }
 462 thead, p.tableblock.header {
 463   font-weight: bold;
 464   color: #527bbd;
 465 }
 466 p.tableblock {
 467   margin-top: 0;
 468 }
 469 table.tableblock {
 470   border-width: 3px;
 471   border-spacing: 0px;
 472   border-style: solid;
 473   border-color: #527bbd;
 474   border-collapse: collapse;
 475 }
 476 th.tableblock, td.tableblock {
 477   border-width: 1px;
 478   padding: 4px;
 479   border-style: solid;
 480   border-color: #527bbd;
 481 }
 482
 483 table.tableblock.frame-topbot {
 484   border-left-style: hidden;
 485   border-right-style: hidden;
 486 }
 487 table.tableblock.frame-sides {
 488   border-top-style: hidden;
 489   border-bottom-style: hidden;
 490 }
 491 table.tableblock.frame-none {
 492   border-style: hidden;
 493 }
 494
 495 th.tableblock.halign-left, td.tableblock.halign-left {
 496   text-align: left;
 497 }
 498 th.tableblock.halign-center, td.tableblock.halign-center {
 499   text-align: center;
 500 }
 501 th.tableblock.halign-right, td.tableblock.halign-right {
 502   text-align: right;
 503 }
 504
 505 th.tableblock.valign-top, td.tableblock.valign-top {
 506   vertical-align: top;
 507 }
 508 th.tableblock.valign-middle, td.tableblock.valign-middle {
 509   vertical-align: middle;
 510 }
 511 th.tableblock.valign-bottom, td.tableblock.valign-bottom {
 512   vertical-align: bottom;
 513 }
 514
 515
 516 /*
 517  * manpage specific
 518  *
 519  * */
 520
 521 body.manpage h1 {
 522   padding-top: 0.5em;
 523   padding-bottom: 0.5em;
 524   border-top: 2px solid silver;
 525   border-bottom: 2px solid silver;
 526 }
 527 body.manpage h2 {
 528   border-style: none;
 529 }
 530 body.manpage div.sectionbody {
 531   margin-left: 3em;
 532 }
 533
 534 @media print {
 535   body.manpage div#toc { display: none; }
 536 }
 537
 538
 539 </style>
 540 <script type="text/javascript">
 541 /*<![CDATA[*/
 542 var asciidoc = {  // Namespace.
 543
 544 /////////////////////////////////////////////////////////////////////
 545 // Table Of Contents generator
 546 /////////////////////////////////////////////////////////////////////
 547
 548 /* Author: Mihai Bazon, September 2002
 549  * http://students.infoiasi.ro/~mishoo
 550  *
 551  * Table Of Content generator
 552  * Version: 0.4
 553  *
 554  * Feel free to use this script under the terms of the GNU General Public
 555  * License, as long as you do not remove or alter this notice.
 556  */
 557
 558  /* modified by Troy D. Hanson, September 2006. License: GPL */
 559  /* modified by Stuart Rackham, 2006, 2009. License: GPL */
 560
 561 // toclevels = 1..4.
 562 toc: function (toclevels) {
 563
 564   function getText(el) {
 565     var text = "";
 566     for (var i = el.firstChild; i != null; i = i.nextSibling) {
 567       if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
 568         text += i.data;
 569       else if (i.firstChild != null)
 570         text += getText(i);
 571     }
 572     return text;
 573   }
 574
 575   function TocEntry(el, text, toclevel) {
 576     this.element = el;
 577     this.text = text;
 578     this.toclevel = toclevel;
 579   }
 580
 581   function tocEntries(el, toclevels) {
 582     var result = new Array;
 583     var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
 584     // Function that scans the DOM tree for header elements (the DOM2
 585     // nodeIterator API would be a better technique but not supported by all
 586     // browsers).
 587     var iterate = function (el) {
 588       for (var i = el.firstChild; i != null; i = i.nextSibling) {
 589         if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
 590           var mo = re.exec(i.tagName);
 591           if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
 592             result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
 593           }
 594           iterate(i);
 595         }
 596       }
 597     }
 598     iterate(el);
 599     return result;
 600   }
 601
 602   var toc = document.getElementById("toc");
 603   if (!toc) {
 604     return;
 605   }
 606
 607   // Delete existing TOC entries in case we're reloading the TOC.
 608   var tocEntriesToRemove = [];
 609   var i;
 610   for (i = 0; i < toc.childNodes.length; i++) {
 611     var entry = toc.childNodes[i];
 612     if (entry.nodeName.toLowerCase() == 'div'
 613      && entry.getAttribute("class")
 614      && entry.getAttribute("class").match(/^toclevel/))
 615       tocEntriesToRemove.push(entry);
 616   }
 617   for (i = 0; i < tocEntriesToRemove.length; i++) {
 618     toc.removeChild(tocEntriesToRemove[i]);
 619   }
 620
 621   // Rebuild TOC entries.
 622   var entries = tocEntries(document.getElementById("content"), toclevels);
 623   for (var i = 0; i < entries.length; ++i) {
 624     var entry = entries[i];
 625     if (entry.element.id == "")
 626       entry.element.id = "_toc_" + i;
 627     var a = document.createElement("a");
 628     a.href = "#" + entry.element.id;
 629     a.appendChild(document.createTextNode(entry.text));
 630     var div = document.createElement("div");
 631     div.appendChild(a);
 632     div.className = "toclevel" + entry.toclevel;
 633     toc.appendChild(div);
 634   }
 635   if (entries.length == 0)
 636     toc.parentNode.removeChild(toc);
 637 },
 638
 639
 640 /////////////////////////////////////////////////////////////////////
 641 // Footnotes generator
 642 /////////////////////////////////////////////////////////////////////
 643
 644 /* Based on footnote generation code from:
 645  * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
 646  */
 647
 648 footnotes: function () {
 649   // Delete existing footnote entries in case we're reloading the footnodes.
 650   var i;
 651   var noteholder = document.getElementById("footnotes");
 652   if (!noteholder) {
 653     return;
 654   }
 655   var entriesToRemove = [];
 656   for (i = 0; i < noteholder.childNodes.length; i++) {
 657     var entry = noteholder.childNodes[i];
 658     if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
 659       entriesToRemove.push(entry);
 660   }
 661   for (i = 0; i < entriesToRemove.length; i++) {
 662     noteholder.removeChild(entriesToRemove[i]);
 663   }
 664
 665   // Rebuild footnote entries.
 666   var cont = document.getElementById("content");
 667   var spans = cont.getElementsByTagName("span");
 668   var refs = {};
 669   var n = 0;
 670   for (i=0; i<spans.length; i++) {
 671     if (spans[i].className == "footnote") {
 672       n++;
 673       var note = spans[i].getAttribute("data-note");
 674       if (!note) {
 675         // Use [\s\S] in place of . so multi-line matches work.
 676         // Because JavaScript has no s (dotall) regex flag.
 677         note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
 678         spans[i].innerHTML =
 679           "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
 680           "' title='View footnote' class='footnote'>" + n + "</a>]";
 681         spans[i].setAttribute("data-note", note);
 682       }
 683       noteholder.innerHTML +=
 684         "<div class='footnote' id='_footnote_" + n + "'>" +
 685         "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
 686         n + "</a>. " + note + "</div>";
 687       var id =spans[i].getAttribute("id");
 688       if (id != null) refs["#"+id] = n;
 689     }
 690   }
 691   if (n == 0)
 692     noteholder.parentNode.removeChild(noteholder);
 693   else {
 694     // Process footnoterefs.
 695     for (i=0; i<spans.length; i++) {
 696       if (spans[i].className == "footnoteref") {
 697         var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
 698         href = href.match(/#.*/)[0];  // Because IE return full URL.
 699         n = refs[href];
 700         spans[i].innerHTML =
 701           "[<a href='#_footnote_" + n +
 702           "' title='View footnote' class='footnote'>" + n + "</a>]";
 703       }
 704     }
 705   }
 706 },
 707
 708 install: function(toclevels) {
 709   var timerId;
 710
 711   function reinstall() {
 712     asciidoc.footnotes();
 713     if (toclevels) {
 714       asciidoc.toc(toclevels);
 715     }
 716   }
 717
 718   function reinstallAndRemoveTimer() {
 719     clearInterval(timerId);
 720     reinstall();
 721   }
 722
 723   timerId = setInterval(reinstall, 500);
 724   if (document.addEventListener)
 725     document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
 726   else
 727     window.onload = reinstallAndRemoveTimer;
 728 }
 729
 730 }
 731 asciidoc.install();
 732 /*]]>*/
 733 </script>
 734 </head>
 735 <body class="manpage">
 736 <div id="header">
 737 <h1>
 738 git-rev-parse(1) Manual Page
 739 </h1>
 740 <h2>NAME</h2>
 741 <div class="sectionbody">
 742 <p>git-rev-parse -
 743    Pick out and massage parameters
 744 </p>
 745 </div>
 746 </div>
 747 <div id="content">
 748 <div class="sect1">
 749 <h2 id="_synopsis">SYNOPSIS</h2>
 750 <div class="sectionbody">
 751 <div class="verseblock">
 752 <pre class="content"><em>git rev-parse</em> [&lt;options&gt;] &lt;args&gt;&#8230;</pre>
 753 <div class="attribution">
 754 </div></div>
 755 </div>
 756 </div>
 757 <div class="sect1">
 758 <h2 id="_description">DESCRIPTION</h2>
 759 <div class="sectionbody">
 760 <div class="paragraph"><p>Many Git porcelainish commands take mixture of flags
 761 (i.e. parameters that begin with a dash <em>-</em>) and parameters
 762 meant for the underlying <em>git rev-list</em> command they use internally
 763 and flags and parameters for the other commands they use
 764 downstream of <em>git rev-list</em>.  This command is used to
 765 distinguish between them.</p></div>
 766 </div>
 767 </div>
 768 <div class="sect1">
 769 <h2 id="_options">OPTIONS</h2>
 770 <div class="sectionbody">
 771 <div class="sect2">
 772 <h3 id="_operation_modes">Operation Modes</h3>
 773 <div class="paragraph"><p>Each of these options must appear first on the command line.</p></div>
 774 <div class="dlist"><dl>
 775 <dt class="hdlist1">
 776 --parseopt
 777 </dt>
 778 <dd>
 779 <p>
 780         Use <em>git rev-parse</em> in option parsing mode (see PARSEOPT section below).
 781 </p>
 782 </dd>
 783 <dt class="hdlist1">
 784 --sq-quote
 785 </dt>
 786 <dd>
 787 <p>
 788         Use <em>git rev-parse</em> in shell quoting mode (see SQ-QUOTE
 789         section below). In contrast to the <code>--sq</code> option below, this
 790         mode does only quoting. Nothing else is done to command input.
 791 </p>
 792 </dd>
 793 </dl></div>
 794 </div>
 795 <div class="sect2">
 796 <h3 id="_options_for_parseopt">Options for --parseopt</h3>
 797 <div class="dlist"><dl>
 798 <dt class="hdlist1">
 799 --keep-dashdash
 800 </dt>
 801 <dd>
 802 <p>
 803         Only meaningful in <code>--parseopt</code> mode. Tells the option parser to echo
 804         out the first <code>--</code> met instead of skipping it.
 805 </p>
 806 </dd>
 807 <dt class="hdlist1">
 808 --stop-at-non-option
 809 </dt>
 810 <dd>
 811 <p>
 812         Only meaningful in <code>--parseopt</code> mode.  Lets the option parser stop at
 813         the first non-option argument.  This can be used to parse sub-commands
 814         that take options themselves.
 815 </p>
 816 </dd>
 817 <dt class="hdlist1">
 818 --stuck-long
 819 </dt>
 820 <dd>
 821 <p>
 822         Only meaningful in <code>--parseopt</code> mode. Output the options in their
 823         long form if available, and with their arguments stuck.
 824 </p>
 825 </dd>
 826 </dl></div>
 827 </div>
 828 <div class="sect2">
 829 <h3 id="_options_for_filtering">Options for Filtering</h3>
 830 <div class="dlist"><dl>
 831 <dt class="hdlist1">
 832 --revs-only
 833 </dt>
 834 <dd>
 835 <p>
 836         Do not output flags and parameters not meant for
 837         <em>git rev-list</em> command.
 838 </p>
 839 </dd>
 840 <dt class="hdlist1">
 841 --no-revs
 842 </dt>
 843 <dd>
 844 <p>
 845         Do not output flags and parameters meant for
 846         <em>git rev-list</em> command.
 847 </p>
 848 </dd>
 849 <dt class="hdlist1">
 850 --flags
 851 </dt>
 852 <dd>
 853 <p>
 854         Do not output non-flag parameters.
 855 </p>
 856 </dd>
 857 <dt class="hdlist1">
 858 --no-flags
 859 </dt>
 860 <dd>
 861 <p>
 862         Do not output flag parameters.
 863 </p>
 864 </dd>
 865 </dl></div>
 866 </div>
 867 <div class="sect2">
 868 <h3 id="_options_for_output">Options for Output</h3>
 869 <div class="dlist"><dl>
 870 <dt class="hdlist1">
 871 --default &lt;arg&gt;
 872 </dt>
 873 <dd>
 874 <p>
 875         If there is no parameter given by the user, use <code>&lt;arg&gt;</code>
 876         instead.
 877 </p>
 878 </dd>
 879 <dt class="hdlist1">
 880 --prefix &lt;arg&gt;
 881 </dt>
 882 <dd>
 883 <p>
 884         Behave as if <em>git rev-parse</em> was invoked from the <code>&lt;arg&gt;</code>
 885         subdirectory of the working tree.  Any relative filenames are
 886         resolved as if they are prefixed by <code>&lt;arg&gt;</code> and will be printed
 887         in that form.
 888 </p>
 889 <div class="paragraph"><p>This can be used to convert arguments to a command run in a subdirectory
 890 so that they can still be used after moving to the top-level of the
 891 repository.  For example:</p></div>
 892 <div class="listingblock">
 893 <div class="content">
 894 <pre><code>prefix=$(git rev-parse --show-prefix)
 895 cd "$(git rev-parse --show-toplevel)"
 896 # rev-parse provides the -- needed for 'set'
 897 eval "set $(git rev-parse --sq --prefix "$prefix" -- "$@")"</code></pre>
 898 </div></div>
 899 </dd>
 900 <dt class="hdlist1">
 901 --verify
 902 </dt>
 903 <dd>
 904 <p>
 905         Verify that exactly one parameter is provided, and that it
 906         can be turned into a raw 20-byte SHA-1 that can be used to
 907         access the object database. If so, emit it to the standard
 908         output; otherwise, error out.
 909 </p>
 910 <div class="paragraph"><p>If you want to make sure that the output actually names an object in
 911 your object database and/or can be used as a specific type of object
 912 you require, you can add the <code>^{type}</code> peeling operator to the parameter.
 913 For example, <code>git rev-parse "$VAR^{commit}"</code> will make sure <code>$VAR</code>
 914 names an existing object that is a commit-ish (i.e. a commit, or an
 915 annotated tag that points at a commit).  To make sure that <code>$VAR</code>
 916 names an existing object of any type, <code>git rev-parse "$VAR^{object}"</code>
 917 can be used.</p></div>
 918 <div class="paragraph"><p>Note that if you are verifying a name from an untrusted source, it is
 919 wise to use <code>--end-of-options</code> so that the name argument is not mistaken
 920 for another option.</p></div>
 921 </dd>
 922 <dt class="hdlist1">
 923 -q
 924 </dt>
 925 <dt class="hdlist1">
 926 --quiet
 927 </dt>
 928 <dd>
 929 <p>
 930         Only meaningful in <code>--verify</code> mode. Do not output an error
 931         message if the first argument is not a valid object name;
 932         instead exit with non-zero status silently.
 933         SHA-1s for valid object names are printed to stdout on success.
 934 </p>
 935 </dd>
 936 <dt class="hdlist1">
 937 --sq
 938 </dt>
 939 <dd>
 940 <p>
 941         Usually the output is made one line per flag and
 942         parameter.  This option makes output a single line,
 943         properly quoted for consumption by shell.  Useful when
 944         you expect your parameter to contain whitespaces and
 945         newlines (e.g. when using pickaxe <code>-S</code> with
 946         <em>git diff-&#42;</em>). In contrast to the <code>--sq-quote</code> option,
 947         the command input is still interpreted as usual.
 948 </p>
 949 </dd>
 950 <dt class="hdlist1">
 951 --short[=length]
 952 </dt>
 953 <dd>
 954 <p>
 955         Same as <code>--verify</code> but shortens the object name to a unique
 956         prefix with at least <code>length</code> characters. The minimum length
 957         is 4, the default is the effective value of the <code>core.abbrev</code>
 958         configuration variable (see <a href="git-config.html">git-config(1)</a>).
 959 </p>
 960 </dd>
 961 <dt class="hdlist1">
 962 --not
 963 </dt>
 964 <dd>
 965 <p>
 966         When showing object names, prefix them with <em>&#94;</em> and
 967         strip <em>&#94;</em> prefix from the object names that already have
 968         one.
 969 </p>
 970 </dd>
 971 <dt class="hdlist1">
 972 --abbrev-ref[=(strict|loose)]
 973 </dt>
 974 <dd>
 975 <p>
 976         A non-ambiguous short name of the objects name.
 977         The option core.warnAmbiguousRefs is used to select the strict
 978         abbreviation mode.
 979 </p>
 980 </dd>
 981 <dt class="hdlist1">
 982 --symbolic
 983 </dt>
 984 <dd>
 985 <p>
 986         Usually the object names are output in SHA-1 form (with
 987         possible <em>&#94;</em> prefix); this option makes them output in a
 988         form as close to the original input as possible.
 989 </p>
 990 </dd>
 991 <dt class="hdlist1">
 992 --symbolic-full-name
 993 </dt>
 994 <dd>
 995 <p>
 996         This is similar to --symbolic, but it omits input that
 997         are not refs (i.e. branch or tag names; or more
 998         explicitly disambiguating "heads/master" form, when you
 999         want to name the "master" branch when there is an
1000         unfortunately named tag "master"), and show them as full
1001         refnames (e.g. "refs/heads/master").
1002 </p>
1003 </dd>
1004 </dl></div>
1005 </div>
1006 <div class="sect2">
1007 <h3 id="_options_for_objects">Options for Objects</h3>
1008 <div class="dlist"><dl>
1009 <dt class="hdlist1">
1010 --all
1011 </dt>
1012 <dd>
1013 <p>
1014         Show all refs found in <code>refs/</code>.
1015 </p>
1016 </dd>
1017 <dt class="hdlist1">
1018 --branches[=pattern]
1019 </dt>
1020 <dt class="hdlist1">
1021 --tags[=pattern]
1022 </dt>
1023 <dt class="hdlist1">
1024 --remotes[=pattern]
1025 </dt>
1026 <dd>
1027 <p>
1028         Show all branches, tags, or remote-tracking branches,
1029         respectively (i.e., refs found in <code>refs/heads</code>,
1030         <code>refs/tags</code>, or <code>refs/remotes</code>, respectively).
1031 </p>
1032 <div class="paragraph"><p>If a <code>pattern</code> is given, only refs matching the given shell glob are
1033 shown.  If the pattern does not contain a globbing character (<code>?</code>,
1034 <code>*</code>, or <code>[</code>), it is turned into a prefix match by appending <code>/*</code>.</p></div>
1035 </dd>
1036 <dt class="hdlist1">
1037 --glob=pattern
1038 </dt>
1039 <dd>
1040 <p>
1041         Show all refs matching the shell glob pattern <code>pattern</code>. If
1042         the pattern does not start with <code>refs/</code>, this is automatically
1043         prepended.  If the pattern does not contain a globbing
1044         character (<code>?</code>, <code>*</code>, or <code>[</code>), it is turned into a prefix
1045         match by appending <code>/*</code>.
1046 </p>
1047 </dd>
1048 <dt class="hdlist1">
1049 --exclude=&lt;glob-pattern&gt;
1050 </dt>
1051 <dd>
1052 <p>
1053         Do not include refs matching <em>&lt;glob-pattern&gt;</em> that the next <code>--all</code>,
1054         <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or <code>--glob</code> would otherwise
1055         consider. Repetitions of this option accumulate exclusion patterns
1056         up to the next <code>--all</code>, <code>--branches</code>, <code>--tags</code>, <code>--remotes</code>, or
1057         <code>--glob</code> option (other options or arguments do not clear
1058         accumulated patterns).
1059 </p>
1060 <div class="paragraph"><p>The patterns given should not begin with <code>refs/heads</code>, <code>refs/tags</code>, or
1061 <code>refs/remotes</code> when applied to <code>--branches</code>, <code>--tags</code>, or <code>--remotes</code>,
1062 respectively, and they must begin with <code>refs/</code> when applied to <code>--glob</code>
1063 or <code>--all</code>. If a trailing <em>/&#42;</em> is intended, it must be given
1064 explicitly.</p></div>
1065 </dd>
1066 <dt class="hdlist1">
1067 --exclude-hidden=[fetch|receive|uploadpack]
1068 </dt>
1069 <dd>
1070 <p>
1071         Do not include refs that would be hidden by <code>git-fetch</code>,
1072         <code>git-receive-pack</code> or <code>git-upload-pack</code> by consulting the appropriate
1073         <code>fetch.hideRefs</code>, <code>receive.hideRefs</code> or <code>uploadpack.hideRefs</code>
1074         configuration along with <code>transfer.hideRefs</code> (see
1075         <a href="git-config.html">git-config(1)</a>). This option affects the next pseudo-ref option
1076         <code>--all</code> or <code>--glob</code> and is cleared after processing them.
1077 </p>
1078 </dd>
1079 <dt class="hdlist1">
1080 --disambiguate=&lt;prefix&gt;
1081 </dt>
1082 <dd>
1083 <p>
1084         Show every object whose name begins with the given prefix.
1085         The &lt;prefix&gt; must be at least 4 hexadecimal digits long to
1086         avoid listing each and every object in the repository by
1087         mistake.
1088 </p>
1089 </dd>
1090 </dl></div>
1091 </div>
1092 <div class="sect2">
1093 <h3 id="_options_for_files">Options for Files</h3>
1094 <div class="dlist"><dl>
1095 <dt class="hdlist1">
1096 --local-env-vars
1097 </dt>
1098 <dd>
1099 <p>
1100         List the GIT_* environment variables that are local to the
1101         repository (e.g. GIT_DIR or GIT_WORK_TREE, but not GIT_EDITOR).
1102         Only the names of the variables are listed, not their value,
1103         even if they are set.
1104 </p>
1105 </dd>
1106 <dt class="hdlist1">
1107 --path-format=(absolute|relative)
1108 </dt>
1109 <dd>
1110 <p>
1111         Controls the behavior of certain other options. If specified as absolute, the
1112         paths printed by those options will be absolute and canonical. If specified as
1113         relative, the paths will be relative to the current working directory if that
1114         is possible.  The default is option specific.
1115 </p>
1116 <div class="paragraph"><p>This option may be specified multiple times and affects only the arguments that
1117 follow it on the command line, either to the end of the command line or the next
1118 instance of this option.</p></div>
1119 </dd>
1120 </dl></div>
1121 <div class="paragraph"><p>The following options are modified by <code>--path-format</code>:</p></div>
1122 <div class="dlist"><dl>
1123 <dt class="hdlist1">
1124 --git-dir
1125 </dt>
1126 <dd>
1127 <p>
1128         Show <code>$GIT_DIR</code> if defined. Otherwise show the path to
1129         the .git directory. The path shown, when relative, is
1130         relative to the current working directory.
1131 </p>
1132 <div class="paragraph"><p>If <code>$GIT_DIR</code> is not defined and the current directory
1133 is not detected to lie in a Git repository or work tree
1134 print a message to stderr and exit with nonzero status.</p></div>
1135 </dd>
1136 <dt class="hdlist1">
1137 --git-common-dir
1138 </dt>
1139 <dd>
1140 <p>
1141         Show <code>$GIT_COMMON_DIR</code> if defined, else <code>$GIT_DIR</code>.
1142 </p>
1143 </dd>
1144 <dt class="hdlist1">
1145 --resolve-git-dir &lt;path&gt;
1146 </dt>
1147 <dd>
1148 <p>
1149         Check if &lt;path&gt; is a valid repository or a gitfile that
1150         points at a valid repository, and print the location of the
1151         repository.  If &lt;path&gt; is a gitfile then the resolved path
1152         to the real repository is printed.
1153 </p>
1154 </dd>
1155 <dt class="hdlist1">
1156 --git-path &lt;path&gt;
1157 </dt>
1158 <dd>
1159 <p>
1160         Resolve "$GIT_DIR/&lt;path&gt;" and takes other path relocation
1161         variables such as $GIT_OBJECT_DIRECTORY,
1162         $GIT_INDEX_FILE&#8230; into account. For example, if
1163         $GIT_OBJECT_DIRECTORY is set to /foo/bar then "git rev-parse
1164         --git-path objects/abc" returns /foo/bar/abc.
1165 </p>
1166 </dd>
1167 <dt class="hdlist1">
1168 --show-toplevel
1169 </dt>
1170 <dd>
1171 <p>
1172         Show the (by default, absolute) path of the top-level directory
1173         of the working tree. If there is no working tree, report an error.
1174 </p>
1175 </dd>
1176 <dt class="hdlist1">
1177 --show-superproject-working-tree
1178 </dt>
1179 <dd>
1180 <p>
1181         Show the absolute path of the root of the superproject&#8217;s
1182         working tree (if exists) that uses the current repository as
1183         its submodule.  Outputs nothing if the current repository is
1184         not used as a submodule by any project.
1185 </p>
1186 </dd>
1187 <dt class="hdlist1">
1188 --shared-index-path
1189 </dt>
1190 <dd>
1191 <p>
1192         Show the path to the shared index file in split index mode, or
1193         empty if not in split-index mode.
1194 </p>
1195 </dd>
1196 </dl></div>
1197 <div class="paragraph"><p>The following options are unaffected by <code>--path-format</code>:</p></div>
1198 <div class="dlist"><dl>
1199 <dt class="hdlist1">
1200 --absolute-git-dir
1201 </dt>
1202 <dd>
1203 <p>
1204         Like <code>--git-dir</code>, but its output is always the canonicalized
1205         absolute path.
1206 </p>
1207 </dd>
1208 <dt class="hdlist1">
1209 --is-inside-git-dir
1210 </dt>
1211 <dd>
1212 <p>
1213         When the current working directory is below the repository
1214         directory print "true", otherwise "false".
1215 </p>
1216 </dd>
1217 <dt class="hdlist1">
1218 --is-inside-work-tree
1219 </dt>
1220 <dd>
1221 <p>
1222         When the current working directory is inside the work tree of the
1223         repository print "true", otherwise "false".
1224 </p>
1225 </dd>
1226 <dt class="hdlist1">
1227 --is-bare-repository
1228 </dt>
1229 <dd>
1230 <p>
1231         When the repository is bare print "true", otherwise "false".
1232 </p>
1233 </dd>
1234 <dt class="hdlist1">
1235 --is-shallow-repository
1236 </dt>
1237 <dd>
1238 <p>
1239         When the repository is shallow print "true", otherwise "false".
1240 </p>
1241 </dd>
1242 <dt class="hdlist1">
1243 --show-cdup
1244 </dt>
1245 <dd>
1246 <p>
1247         When the command is invoked from a subdirectory, show the
1248         path of the top-level directory relative to the current
1249         directory (typically a sequence of "../", or an empty string).
1250 </p>
1251 </dd>
1252 <dt class="hdlist1">
1253 --show-prefix
1254 </dt>
1255 <dd>
1256 <p>
1257         When the command is invoked from a subdirectory, show the
1258         path of the current directory relative to the top-level
1259         directory.
1260 </p>
1261 </dd>
1262 <dt class="hdlist1">
1263 --show-object-format[=(storage|input|output)]
1264 </dt>
1265 <dd>
1266 <p>
1267         Show the object format (hash algorithm) used for the repository
1268         for storage inside the <code>.git</code> directory, input, or output. For
1269         input, multiple algorithms may be printed, space-separated.
1270         If not specified, the default is "storage".
1271 </p>
1272 </dd>
1273 </dl></div>
1274 </div>
1275 <div class="sect2">
1276 <h3 id="_other_options">Other Options</h3>
1277 <div class="dlist"><dl>
1278 <dt class="hdlist1">
1279 --since=datestring
1280 </dt>
1281 <dt class="hdlist1">
1282 --after=datestring
1283 </dt>
1284 <dd>
1285 <p>
1286         Parse the date string, and output the corresponding
1287         --max-age= parameter for <em>git rev-list</em>.
1288 </p>
1289 </dd>
1290 <dt class="hdlist1">
1291 --until=datestring
1292 </dt>
1293 <dt class="hdlist1">
1294 --before=datestring
1295 </dt>
1296 <dd>
1297 <p>
1298         Parse the date string, and output the corresponding
1299         --min-age= parameter for <em>git rev-list</em>.
1300 </p>
1301 </dd>
1302 <dt class="hdlist1">
1303 &lt;args&gt;&#8230;
1304 </dt>
1305 <dd>
1306 <p>
1307         Flags and parameters to be parsed.
1308 </p>
1309 </dd>
1310 </dl></div>
1311 </div>
1312 </div>
1313 </div>
1314 <div class="sect1">
1315 <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
1316 <div class="sectionbody">
1317 <div class="paragraph"><p>A revision parameter <em>&lt;rev&gt;</em> typically, but not necessarily, names a
1318 commit object.  It uses what is called an <em>extended SHA-1</em>
1319 syntax.  Here are various ways to spell object names.  The
1320 ones listed near the end of this list name trees and
1321 blobs contained in a commit.</p></div>
1322 <div class="admonitionblock">
1323 <table><tr>
1324 <td class="icon">
1325 <div class="title">Note</div>
1326 </td>
1327 <td class="content">This document shows the "raw" syntax as seen by git. The shell
1328 and other UIs might require additional quoting to protect special
1329 characters and to avoid word splitting.</td>
1330 </tr></table>
1331 </div>
1332 <div class="dlist"><dl>
1333 <dt class="hdlist1">
1334 <em>&lt;sha1&gt;</em>, e.g. <em>dae86e1950b1277e545cee180551750029cfe735</em>, <em>dae86e</em>
1335 </dt>
1336 <dd>
1337 <p>
1338   The full SHA-1 object name (40-byte hexadecimal string), or
1339   a leading substring that is unique within the repository.
1340   E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both
1341   name the same commit object if there is no other object in
1342   your repository whose object name starts with dae86e.
1343 </p>
1344 </dd>
1345 <dt class="hdlist1">
1346 <em>&lt;describeOutput&gt;</em>, e.g. <em>v1.7.4.2-679-g3bee7fb</em>
1347 </dt>
1348 <dd>
1349 <p>
1350   Output from <code>git describe</code>; i.e. a closest tag, optionally
1351   followed by a dash and a number of commits, followed by a dash, a
1352   <em>g</em>, and an abbreviated object name.
1353 </p>
1354 </dd>
1355 <dt class="hdlist1">
1356 <em>&lt;refname&gt;</em>, e.g. <em>master</em>, <em>heads/master</em>, <em>refs/heads/master</em>
1357 </dt>
1358 <dd>
1359 <p>
1360   A symbolic ref name.  E.g. <em>master</em> typically means the commit
1361   object referenced by <em>refs/heads/master</em>.  If you
1362   happen to have both <em>heads/master</em> and <em>tags/master</em>, you can
1363   explicitly say <em>heads/master</em> to tell Git which one you mean.
1364   When ambiguous, a <em>&lt;refname&gt;</em> is disambiguated by taking the
1365   first match in the following rules:
1366 </p>
1367 <div class="olist arabic"><ol class="arabic">
1368 <li>
1369 <p>
1370 If <em>$GIT_DIR/&lt;refname&gt;</em> exists, that is what you mean (this is usually
1371     useful only for <code>HEAD</code>, <code>FETCH_HEAD</code>, <code>ORIG_HEAD</code>, <code>MERGE_HEAD</code>,
1372     <code>REBASE_HEAD</code>, <code>REVERT_HEAD</code>, <code>CHERRY_PICK_HEAD</code>, <code>BISECT_HEAD</code>
1373     and <code>AUTO_MERGE</code>);
1374 </p>
1375 </li>
1376 <li>
1377 <p>
1378 otherwise, <em>refs/&lt;refname&gt;</em> if it exists;
1379 </p>
1380 </li>
1381 <li>
1382 <p>
1383 otherwise, <em>refs/tags/&lt;refname&gt;</em> if it exists;
1384 </p>
1385 </li>
1386 <li>
1387 <p>
1388 otherwise, <em>refs/heads/&lt;refname&gt;</em> if it exists;
1389 </p>
1390 </li>
1391 <li>
1392 <p>
1393 otherwise, <em>refs/remotes/&lt;refname&gt;</em> if it exists;
1394 </p>
1395 </li>
1396 <li>
1397 <p>
1398 otherwise, <em>refs/remotes/&lt;refname&gt;/HEAD</em> if it exists.
1399 </p>
1400 </li>
1401 </ol></div>
1402 <div class="dlist"><dl>
1403 <dt class="hdlist1">
1404 <code>HEAD</code>
1405 </dt>
1406 <dd>
1407 <p>
1408     names the commit on which you based the changes in the working tree.
1409 </p>
1410 </dd>
1411 <dt class="hdlist1">
1412 <code>FETCH_HEAD</code>
1413 </dt>
1414 <dd>
1415 <p>
1416     records the branch which you fetched from a remote repository with
1417     your last <code>git fetch</code> invocation.
1418 </p>
1419 </dd>
1420 <dt class="hdlist1">
1421 <code>ORIG_HEAD</code>
1422 </dt>
1423 <dd>
1424 <p>
1425     is created by commands that move your <code>HEAD</code> in a drastic way (<code>git
1426     am</code>, <code>git merge</code>, <code>git rebase</code>, <code>git reset</code>), to record the position
1427     of the <code>HEAD</code> before their operation, so that you can easily change
1428     the tip of the branch back to the state before you ran them.
1429 </p>
1430 </dd>
1431 <dt class="hdlist1">
1432 <code>MERGE_HEAD</code>
1433 </dt>
1434 <dd>
1435 <p>
1436     records the commit(s) which you are merging into your branch when you
1437     run <code>git merge</code>.
1438 </p>
1439 </dd>
1440 <dt class="hdlist1">
1441 <code>REBASE_HEAD</code>
1442 </dt>
1443 <dd>
1444 <p>
1445     during a rebase, records the commit at which the operation is
1446     currently stopped, either because of conflicts or an <code>edit</code> command in
1447     an interactive rebase.
1448 </p>
1449 </dd>
1450 <dt class="hdlist1">
1451 <code>REVERT_HEAD</code>
1452 </dt>
1453 <dd>
1454 <p>
1455     records the commit which you are reverting when you run <code>git revert</code>.
1456 </p>
1457 </dd>
1458 <dt class="hdlist1">
1459 <code>CHERRY_PICK_HEAD</code>
1460 </dt>
1461 <dd>
1462 <p>
1463     records the commit which you are cherry-picking when you run <code>git
1464     cherry-pick</code>.
1465 </p>
1466 </dd>
1467 <dt class="hdlist1">
1468 <code>BISECT_HEAD</code>
1469 </dt>
1470 <dd>
1471 <p>
1472     records the current commit to be tested when you run <code>git bisect
1473     --no-checkout</code>.
1474 </p>
1475 </dd>
1476 <dt class="hdlist1">
1477 <code>AUTO_MERGE</code>
1478 </dt>
1479 <dd>
1480 <p>
1481     records a tree object corresponding to the state the
1482     <em>ort</em> merge strategy wrote to the working tree when a merge operation
1483     resulted in conflicts.
1484 </p>
1485 </dd>
1486 </dl></div>
1487 <div class="paragraph"><p>Note that any of the <em>refs/*</em> cases above may come either from
1488 the <code>$GIT_DIR/refs</code> directory or from the <code>$GIT_DIR/packed-refs</code> file.
1489 While the ref name encoding is unspecified, UTF-8 is preferred as
1490 some output processing may assume ref names in UTF-8.</p></div>
1491 </dd>
1492 <dt class="hdlist1">
1493 <em>@</em>
1494 </dt>
1495 <dd>
1496 <p>
1497   <em>@</em> alone is a shortcut for <code>HEAD</code>.
1498 </p>
1499 </dd>
1500 <dt class="hdlist1">
1501 <em>[&lt;refname&gt;]@{&lt;date&gt;}</em>, e.g. <em>master@{yesterday}</em>, <em>HEAD@{5 minutes ago}</em>
1502 </dt>
1503 <dd>
1504 <p>
1505   A ref followed by the suffix <em>@</em> with a date specification
1506   enclosed in a brace
1507   pair (e.g. <em>{yesterday}</em>, <em>{1 month 2 weeks 3 days 1 hour 1
1508   second ago}</em> or <em>{1979-02-26 18:30:00}</em>) specifies the value
1509   of the ref at a prior point in time.  This suffix may only be
1510   used immediately following a ref name and the ref must have an
1511   existing log (<em>$GIT_DIR/logs/&lt;ref&gt;</em>). Note that this looks up the state
1512   of your <strong>local</strong> ref at a given time; e.g., what was in your local
1513   <em>master</em> branch last week. If you want to look at commits made during
1514   certain times, see <code>--since</code> and <code>--until</code>.
1515 </p>
1516 </dd>
1517 <dt class="hdlist1">
1518 <em>&lt;refname&gt;@{&lt;n&gt;}</em>, e.g. <em>master@{1}</em>
1519 </dt>
1520 <dd>
1521 <p>
1522   A ref followed by the suffix <em>@</em> with an ordinal specification
1523   enclosed in a brace pair (e.g. <em>{1}</em>, <em>{15}</em>) specifies
1524   the n-th prior value of that ref.  For example <em>master@{1}</em>
1525   is the immediate prior value of <em>master</em> while <em>master@{5}</em>
1526   is the 5th prior value of <em>master</em>. This suffix may only be used
1527   immediately following a ref name and the ref must have an existing
1528   log (<em>$GIT_DIR/logs/&lt;refname&gt;</em>).
1529 </p>
1530 </dd>
1531 <dt class="hdlist1">
1532 <em>@{&lt;n&gt;}</em>, e.g. <em>@{1}</em>
1533 </dt>
1534 <dd>
1535 <p>
1536   You can use the <em>@</em> construct with an empty ref part to get at a
1537   reflog entry of the current branch. For example, if you are on
1538   branch <em>blabla</em> then <em>@{1}</em> means the same as <em>blabla@{1}</em>.
1539 </p>
1540 </dd>
1541 <dt class="hdlist1">
1542 <em>@{-&lt;n&gt;}</em>, e.g. <em>@{-1}</em>
1543 </dt>
1544 <dd>
1545 <p>
1546   The construct <em>@{-&lt;n&gt;}</em> means the &lt;n&gt;th branch/commit checked out
1547   before the current one.
1548 </p>
1549 </dd>
1550 <dt class="hdlist1">
1551 <em>[&lt;branchname&gt;]@{upstream}</em>, e.g. <em>master@{upstream}</em>, <em>@{u}</em>
1552 </dt>
1553 <dd>
1554 <p>
1555   A branch B may be set up to build on top of a branch X (configured with
1556   <code>branch.&lt;name&gt;.merge</code>) at a remote R (configured with
1557   the branch X taken from remote R, typically found at <code>refs/remotes/R/X</code>.
1558 </p>
1559 </dd>
1560 <dt class="hdlist1">
1561 <em>[&lt;branchname&gt;]@{push}</em>, e.g. <em>master@{push}</em>, <em>@{push}</em>
1562 </dt>
1563 <dd>
1564 <p>
1565   The suffix <em>@{push}</em> reports the branch "where we would push to" if
1566   <code>git push</code> were run while <code>branchname</code> was checked out (or the current
1567   <code>HEAD</code> if no branchname is specified). Like for <em>@{upstream}</em>, we report
1568   the remote-tracking branch that corresponds to that branch at the remote.
1569 </p>
1570 <div class="paragraph"><p>Here&#8217;s an example to make it more clear:</p></div>
1571 <div class="listingblock">
1572 <div class="content">
1573 <pre><code>$ git config push.default current
1574 $ git config remote.pushdefault myfork
1575 $ git switch -c mybranch origin/master
1576
1577 $ git rev-parse --symbolic-full-name @{upstream}
1578 refs/remotes/origin/master
1579
1580 $ git rev-parse --symbolic-full-name @{push}
1581 refs/remotes/myfork/mybranch</code></pre>
1582 </div></div>
1583 <div class="paragraph"><p>Note in the example that we set up a triangular workflow, where we pull
1584 from one location and push to another. In a non-triangular workflow,
1585 <em>@{push}</em> is the same as <em>@{upstream}</em>, and there is no need for it.</p></div>
1586 <div class="paragraph"><p>This suffix is also accepted when spelled in uppercase, and means the same
1587 thing no matter the case.</p></div>
1588 </dd>
1589 <dt class="hdlist1">
1590 <em>&lt;rev&gt;&#94;[&lt;n&gt;]</em>, e.g. <em>HEAD&#94;, v1.5.1&#94;0</em>
1591 </dt>
1592 <dd>
1593 <p>
1594   A suffix <em>&#94;</em> to a revision parameter means the first parent of
1595   that commit object.  <em>&#94;&lt;n&gt;</em> means the &lt;n&gt;th parent (i.e.
1596   <em>&lt;rev&gt;&#94;</em>
1597   is equivalent to <em>&lt;rev&gt;&#94;1</em>).  As a special rule,
1598   <em>&lt;rev&gt;&#94;0</em> means the commit itself and is used when <em>&lt;rev&gt;</em> is the
1599   object name of a tag object that refers to a commit object.
1600 </p>
1601 </dd>
1602 <dt class="hdlist1">
1603 <em>&lt;rev&gt;&#126;[&lt;n&gt;]</em>, e.g. <em>HEAD&#126;, master&#126;3</em>
1604 </dt>
1605 <dd>
1606 <p>
1607   A suffix <em>&#126;</em> to a revision parameter means the first parent of
1608   that commit object.
1609   A suffix <em>&#126;&lt;n&gt;</em> to a revision parameter means the commit
1610   object that is the &lt;n&gt;th generation ancestor of the named
1611   commit object, following only the first parents.  I.e. <em>&lt;rev&gt;&#126;3</em> is
1612   equivalent to <em>&lt;rev&gt;&#94;&#94;&#94;</em> which is equivalent to
1613   <em>&lt;rev&gt;&#94;1&#94;1&#94;1</em>.  See below for an illustration of
1614   the usage of this form.
1615 </p>
1616 </dd>
1617 <dt class="hdlist1">
1618 <em>&lt;rev&gt;&#94;{&lt;type&gt;}</em>, e.g. <em>v0.99.8&#94;{commit}</em>
1619 </dt>
1620 <dd>
1621 <p>
1622   A suffix <em>&#94;</em> followed by an object type name enclosed in
1623   brace pair means dereference the object at <em>&lt;rev&gt;</em> recursively until
1624   an object of type <em>&lt;type&gt;</em> is found or the object cannot be
1625   dereferenced anymore (in which case, barf).
1626   For example, if <em>&lt;rev&gt;</em> is a commit-ish, <em>&lt;rev&gt;&#94;{commit}</em>
1627   describes the corresponding commit object.
1628   Similarly, if <em>&lt;rev&gt;</em> is a tree-ish, <em>&lt;rev&gt;&#94;{tree}</em>
1629   describes the corresponding tree object.
1630   <em>&lt;rev&gt;&#94;0</em>
1631   is a short-hand for <em>&lt;rev&gt;&#94;{commit}</em>.
1632 </p>
1633 <div class="paragraph"><p><em>&lt;rev&gt;&#94;{object}</em> can be used to make sure <em>&lt;rev&gt;</em> names an
1634 object that exists, without requiring <em>&lt;rev&gt;</em> to be a tag, and
1635 without dereferencing <em>&lt;rev&gt;</em>; because a tag is already an object,
1636 it does not have to be dereferenced even once to get to an object.</p></div>
1637 <div class="paragraph"><p><em>&lt;rev&gt;&#94;{tag}</em> can be used to ensure that <em>&lt;rev&gt;</em> identifies an
1638 existing tag object.</p></div>
1639 </dd>
1640 <dt class="hdlist1">
1641 <em>&lt;rev&gt;&#94;{}</em>, e.g. <em>v0.99.8&#94;{}</em>
1642 </dt>
1643 <dd>
1644 <p>
1645   A suffix <em>&#94;</em> followed by an empty brace pair
1646   means the object could be a tag,
1647   and dereference the tag recursively until a non-tag object is
1648   found.
1649 </p>
1650 </dd>
1651 <dt class="hdlist1">
1652 <em>&lt;rev&gt;&#94;{/&lt;text&gt;}</em>, e.g. <em>HEAD^{/fix nasty bug}</em>
1653 </dt>
1654 <dd>
1655 <p>
1656   A suffix <em>&#94;</em> to a revision parameter, followed by a brace
1657   pair that contains a text led by a slash,
1658   is the same as the <em>:/fix nasty bug</em> syntax below except that
1659   it returns the youngest matching commit which is reachable from
1660   the <em>&lt;rev&gt;</em> before <em>&#94;</em>.
1661 </p>
1662 </dd>
1663 <dt class="hdlist1">
1664 <em>:/&lt;text&gt;</em>, e.g. <em>:/fix nasty bug</em>
1665 </dt>
1666 <dd>
1667 <p>
1668   A colon, followed by a slash, followed by a text, names
1669   a commit whose commit message matches the specified regular expression.
1670   This name returns the youngest matching commit which is
1671   reachable from any ref, including HEAD.
1672   The regular expression can match any part of the
1673   commit message. To match messages starting with a string, one can use
1674   e.g. <em>:/^foo</em>. The special sequence <em>:/!</em> is reserved for modifiers to what
1675   is matched. <em>:/!-foo</em> performs a negative match, while <em>:/!!foo</em> matches a
1676   literal <em>!</em> character, followed by <em>foo</em>. Any other sequence beginning with
1677   <em>:/!</em> is reserved for now.
1678   Depending on the given text, the shell&#8217;s word splitting rules might
1679   require additional quoting.
1680 </p>
1681 </dd>
1682 <dt class="hdlist1">
1683 <em>&lt;rev&gt;:&lt;path&gt;</em>, e.g. <em>HEAD:README</em>, <em>master:./README</em>
1684 </dt>
1685 <dd>
1686 <p>
1687   A suffix <em>:</em> followed by a path names the blob or tree
1688   at the given path in the tree-ish object named by the part
1689   before the colon.
1690   A path starting with <em>./</em> or <em>../</em> is relative to the current working directory.
1691   The given path will be converted to be relative to the working tree&#8217;s root directory.
1692   This is most useful to address a blob or tree from a commit or tree that has
1693   the same tree structure as the working tree.
1694 </p>
1695 </dd>
1696 <dt class="hdlist1">
1697 <em>:[&lt;n&gt;:]&lt;path&gt;</em>, e.g. <em>:0:README</em>, <em>:README</em>
1698 </dt>
1699 <dd>
1700 <p>
1701   A colon, optionally followed by a stage number (0 to 3) and a
1702   colon, followed by a path, names a blob object in the
1703   index at the given path. A missing stage number (and the colon
1704   that follows it) names a stage 0 entry. During a merge, stage
1705   1 is the common ancestor, stage 2 is the target branch&#8217;s version
1706   (typically the current branch), and stage 3 is the version from
1707   the branch which is being merged.
1708 </p>
1709 </dd>
1710 </dl></div>
1711 <div class="paragraph"><p>Here is an illustration, by Jon Loeliger.  Both commit nodes B
1712 and C are parents of commit node A.  Parent commits are ordered
1713 left-to-right.</p></div>
1714 <div class="literalblock">
1715 <div class="content">
1716 <pre><code>G   H   I   J
1717  \ /     \ /
1718   D   E   F
1719    \  |  / \
1720     \ | /   |
1721      \|/    |
1722       B     C
1723        \   /
1724         \ /
1725          A</code></pre>
1726 </div></div>
1727 <div class="literalblock">
1728 <div class="content">
1729 <pre><code>A =      = A^0
1730 B = A^   = A^1     = A~1
1731 C =      = A^2
1732 D = A^^  = A^1^1   = A~2
1733 E = B^2  = A^^2
1734 F = B^3  = A^^3
1735 G = A^^^ = A^1^1^1 = A~3
1736 H = D^2  = B^^2    = A^^^2  = A~2^2
1737 I = F^   = B^3^    = A^^3^
1738 J = F^2  = B^3^2   = A^^3^2</code></pre>
1739 </div></div>
1740 </div>
1741 </div>
1742 <div class="sect1">
1743 <h2 id="_specifying_ranges">SPECIFYING RANGES</h2>
1744 <div class="sectionbody">
1745 <div class="paragraph"><p>History traversing commands such as <code>git log</code> operate on a set
1746 of commits, not just a single commit.</p></div>
1747 <div class="paragraph"><p>For these commands,
1748 specifying a single revision, using the notation described in the
1749 previous section, means the set of commits <code>reachable</code> from the given
1750 commit.</p></div>
1751 <div class="paragraph"><p>Specifying several revisions means the set of commits reachable from
1752 any of the given commits.</p></div>
1753 <div class="paragraph"><p>A commit&#8217;s reachable set is the commit itself and the commits in
1754 its ancestry chain.</p></div>
1755 <div class="paragraph"><p>There are several notations to specify a set of connected commits
1756 (called a "revision range"), illustrated below.</p></div>
1757 <div class="sect2">
1758 <h3 id="_commit_exclusions">Commit Exclusions</h3>
1759 <div class="dlist"><dl>
1760 <dt class="hdlist1">
1761 <em>&#94;&lt;rev&gt;</em> (caret) Notation
1762 </dt>
1763 <dd>
1764 <p>
1765  To exclude commits reachable from a commit, a prefix <em>&#94;</em>
1766  notation is used.  E.g. <em>&#94;r1 r2</em> means commits reachable
1767  from <em>r2</em> but exclude the ones reachable from <em>r1</em> (i.e. <em>r1</em> and
1768  its ancestors).
1769 </p>
1770 </dd>
1771 </dl></div>
1772 </div>
1773 <div class="sect2">
1774 <h3 id="_dotted_range_notations">Dotted Range Notations</h3>
1775 <div class="dlist"><dl>
1776 <dt class="hdlist1">
1777 The <em>..</em> (two-dot) Range Notation
1778 </dt>
1779 <dd>
1780 <p>
1781  The <em>&#94;r1 r2</em> set operation appears so often that there is a shorthand
1782  for it.  When you have two commits <em>r1</em> and <em>r2</em> (named according
1783  to the syntax explained in SPECIFYING REVISIONS above), you can ask
1784  for commits that are reachable from r2 excluding those that are reachable
1785  from r1 by <em>&#94;r1 r2</em> and it can be written as <em>r1..r2</em>.
1786 </p>
1787 </dd>
1788 <dt class="hdlist1">
1789 The <em>...</em> (three-dot) Symmetric Difference Notation
1790 </dt>
1791 <dd>
1792 <p>
1793  A similar notation <em>r1...r2</em> is called symmetric difference
1794  of <em>r1</em> and <em>r2</em> and is defined as
1795  <em>r1 r2 --not $(git merge-base --all r1 r2)</em>.
1796  It is the set of commits that are reachable from either one of
1797  <em>r1</em> (left side) or <em>r2</em> (right side) but not from both.
1798 </p>
1799 </dd>
1800 </dl></div>
1801 <div class="paragraph"><p>In these two shorthand notations, you can omit one end and let it default to HEAD.
1802 For example, <em>origin..</em> is a shorthand for <em>origin..HEAD</em> and asks "What
1803 did I do since I forked from the origin branch?"  Similarly, <em>..origin</em>
1804 is a shorthand for <em>HEAD..origin</em> and asks "What did the origin do since
1805 I forked from them?"  Note that <em>..</em> would mean <em>HEAD..HEAD</em> which is an
1806 empty range that is both reachable and unreachable from HEAD.</p></div>
1807 <div class="paragraph"><p>Commands that are specifically designed to take two distinct ranges
1808 (e.g. "git range-diff R1 R2" to compare two ranges) do exist, but
1809 they are exceptions.  Unless otherwise noted, all "git" commands
1810 that operate on a set of commits work on a single revision range.
1811 In other words, writing two "two-dot range notation" next to each
1812 other, e.g.</p></div>
1813 <div class="literalblock">
1814 <div class="content">
1815 <pre><code>$ git log A..B C..D</code></pre>
1816 </div></div>
1817 <div class="paragraph"><p>does <strong>not</strong> specify two revision ranges for most commands.  Instead
1818 it will name a single connected set of commits, i.e. those that are
1819 reachable from either B or D but are reachable from neither A or C.
1820 In a linear history like this:</p></div>
1821 <div class="literalblock">
1822 <div class="content">
1823 <pre><code>---A---B---o---o---C---D</code></pre>
1824 </div></div>
1825 <div class="paragraph"><p>because A and B are reachable from C, the revision range specified
1826 by these two dotted ranges is a single commit D.</p></div>
1827 </div>
1828 <div class="sect2">
1829 <h3 id="_other_lt_rev_gt_94_parent_shorthand_notations">Other &lt;rev&gt;&#94; Parent Shorthand Notations</h3>
1830 <div class="paragraph"><p>Three other shorthands exist, particularly useful for merge commits,
1831 for naming a set that is formed by a commit and its parent commits.</p></div>
1832 <div class="paragraph"><p>The <em>r1&#94;@</em> notation means all parents of <em>r1</em>.</p></div>
1833 <div class="paragraph"><p>The <em>r1&#94;!</em> notation includes commit <em>r1</em> but excludes all of its parents.
1834 By itself, this notation denotes the single commit <em>r1</em>.</p></div>
1835 <div class="paragraph"><p>The <em>&lt;rev&gt;&#94;-[&lt;n&gt;]</em> notation includes <em>&lt;rev&gt;</em> but excludes the &lt;n&gt;th
1836 parent (i.e. a shorthand for <em>&lt;rev&gt;&#94;&lt;n&gt;..&lt;rev&gt;</em>), with <em>&lt;n&gt;</em> = 1 if
1837 not given. This is typically useful for merge commits where you
1838 can just pass <em>&lt;commit&gt;&#94;-</em> to get all the commits in the branch
1839 that was merged in merge commit <em>&lt;commit&gt;</em> (including <em>&lt;commit&gt;</em>
1840 itself).</p></div>
1841 <div class="paragraph"><p>While <em>&lt;rev&gt;&#94;&lt;n&gt;</em> was about specifying a single commit parent, these
1842 three notations also consider its parents. For example you can say
1843 <em>HEAD&#94;2&#94;@</em>, however you cannot say <em>HEAD&#94;@&#94;2</em>.</p></div>
1844 </div>
1845 </div>
1846 </div>
1847 <div class="sect1">
1848 <h2 id="_revision_range_summary">Revision Range Summary</h2>
1849 <div class="sectionbody">
1850 <div class="dlist"><dl>
1851 <dt class="hdlist1">
1852 <em>&lt;rev&gt;</em>
1853 </dt>
1854 <dd>
1855 <p>
1856         Include commits that are reachable from &lt;rev&gt; (i.e. &lt;rev&gt; and its
1857         ancestors).
1858 </p>
1859 </dd>
1860 <dt class="hdlist1">
1861 <em>&#94;&lt;rev&gt;</em>
1862 </dt>
1863 <dd>
1864 <p>
1865         Exclude commits that are reachable from &lt;rev&gt; (i.e. &lt;rev&gt; and its
1866         ancestors).
1867 </p>
1868 </dd>
1869 <dt class="hdlist1">
1870 <em>&lt;rev1&gt;..&lt;rev2&gt;</em>
1871 </dt>
1872 <dd>
1873 <p>
1874         Include commits that are reachable from &lt;rev2&gt; but exclude
1875         those that are reachable from &lt;rev1&gt;.  When either &lt;rev1&gt; or
1876         &lt;rev2&gt; is omitted, it defaults to <code>HEAD</code>.
1877 </p>
1878 </dd>
1879 <dt class="hdlist1">
1880 <em>&lt;rev1&gt;...&lt;rev2&gt;</em>
1881 </dt>
1882 <dd>
1883 <p>
1884         Include commits that are reachable from either &lt;rev1&gt; or
1885         &lt;rev2&gt; but exclude those that are reachable from both.  When
1886         either &lt;rev1&gt; or &lt;rev2&gt; is omitted, it defaults to <code>HEAD</code>.
1887 </p>
1888 </dd>
1889 <dt class="hdlist1">
1890 <em>&lt;rev&gt;&#94;@</em>, e.g. <em>HEAD&#94;@</em>
1891 </dt>
1892 <dd>
1893 <p>
1894   A suffix <em>&#94;</em> followed by an at sign is the same as listing
1895   all parents of <em>&lt;rev&gt;</em> (meaning, include anything reachable from
1896   its parents, but not the commit itself).
1897 </p>
1898 </dd>
1899 <dt class="hdlist1">
1900 <em>&lt;rev&gt;&#94;!</em>, e.g. <em>HEAD&#94;!</em>
1901 </dt>
1902 <dd>
1903 <p>
1904   A suffix <em>&#94;</em> followed by an exclamation mark is the same
1905   as giving commit <em>&lt;rev&gt;</em> and all its parents prefixed with
1906   <em>&#94;</em> to exclude them (and their ancestors).
1907 </p>
1908 </dd>
1909 <dt class="hdlist1">
1910 <em>&lt;rev&gt;&#94;-&lt;n&gt;</em>, e.g. <em>HEAD&#94;-, HEAD&#94;-2</em>
1911 </dt>
1912 <dd>
1913 <p>
1914         Equivalent to <em>&lt;rev&gt;&#94;&lt;n&gt;..&lt;rev&gt;</em>, with <em>&lt;n&gt;</em> = 1 if not
1915         given.
1916 </p>
1917 </dd>
1918 </dl></div>
1919 <div class="paragraph"><p>Here are a handful of examples using the Loeliger illustration above,
1920 with each step in the notation&#8217;s expansion and selection carefully
1921 spelt out:</p></div>
1922 <div class="literalblock">
1923 <div class="content">
1924 <pre><code>   Args   Expanded arguments    Selected commits
1925    D                            G H D
1926    D F                          G H I J D F
1927    ^G D                         H D
1928    ^D B                         E I J F B
1929    ^D B C                       E I J F B C
1930    C                            I J F C
1931    B..C   = ^B C                C
1932    B...C  = B ^F C              G H D E B C
1933    B^-    = B^..B
1934           = ^B^1 B              E I J F B
1935    C^@    = C^1
1936           = F                   I J F
1937    B^@    = B^1 B^2 B^3
1938           = D E F               D G H E F I J
1939    C^!    = C ^C^@
1940           = C ^C^1
1941           = C ^F                C
1942    B^!    = B ^B^@
1943           = B ^B^1 ^B^2 ^B^3
1944           = B ^D ^E ^F          B
1945    F^! D  = F ^I ^J D           G H D F</code></pre>
1946 </div></div>
1947 </div>
1948 </div>
1949 <div class="sect1">
1950 <h2 id="_parseopt">PARSEOPT</h2>
1951 <div class="sectionbody">
1952 <div class="paragraph"><p>In <code>--parseopt</code> mode, <em>git rev-parse</em> helps massaging options to bring to shell
1953 scripts the same facilities C builtins have. It works as an option normalizer
1954 (e.g. splits single switches aggregate values), a bit like <code>getopt(1)</code> does.</p></div>
1955 <div class="paragraph"><p>It takes on the standard input the specification of the options to parse and
1956 understand, and echoes on the standard output a string suitable for <code>sh(1)</code> <code>eval</code>
1957 to replace the arguments with normalized ones.  In case of error, it outputs
1958 usage on the standard error stream, and exits with code 129.</p></div>
1959 <div class="paragraph"><p>Note: Make sure you quote the result when passing it to <code>eval</code>.  See
1960 below for an example.</p></div>
1961 <div class="sect2">
1962 <h3 id="_input_format">Input Format</h3>
1963 <div class="paragraph"><p><em>git rev-parse --parseopt</em> input format is fully text based. It has two parts,
1964 separated by a line that contains only <code>--</code>. The lines before the separator
1965 (should be one or more) are used for the usage.
1966 The lines after the separator describe the options.</p></div>
1967 <div class="paragraph"><p>Each line of options has this format:</p></div>
1968 <div class="listingblock">
1969 <div class="content">
1970 <pre><code>&lt;opt-spec&gt;&lt;flags&gt;*&lt;arg-hint&gt;? SP+ help LF</code></pre>
1971 </div></div>
1972 <div class="dlist"><dl>
1973 <dt class="hdlist1">
1974 <code>&lt;opt-spec&gt;</code>
1975 </dt>
1976 <dd>
1977 <p>
1978         its format is the short option character, then the long option name
1979         separated by a comma. Both parts are not required, though at least one
1980         is necessary. May not contain any of the <code>&lt;flags&gt;</code> characters.
1981         <code>h,help</code>, <code>dry-run</code> and <code>f</code> are examples of correct <code>&lt;opt-spec&gt;</code>.
1982 </p>
1983 </dd>
1984 <dt class="hdlist1">
1985 <code>&lt;flags&gt;</code>
1986 </dt>
1987 <dd>
1988 <p>
1989         <code>&lt;flags&gt;</code> are of <code>*</code>, <code>=</code>, <code>?</code> or <code>!</code>.
1990 </p>
1991 <div class="ulist"><ul>
1992 <li>
1993 <p>
1994 Use <code>=</code> if the option takes an argument.
1995 </p>
1996 </li>
1997 <li>
1998 <p>
1999 Use <code>?</code> to mean that the option takes an optional argument. You
2000           probably want to use the <code>--stuck-long</code> mode to be able to
2001           unambiguously parse the optional argument.
2002 </p>
2003 </li>
2004 <li>
2005 <p>
2006 Use <code>*</code> to mean that this option should not be listed in the usage
2007           generated for the <code>-h</code> argument. It&#8217;s shown for <code>--help-all</code> as
2008           documented in <a href="gitcli.html">gitcli(7)</a>.
2009 </p>
2010 </li>
2011 <li>
2012 <p>
2013 Use <code>!</code> to not make the corresponding negated long option available.
2014 </p>
2015 </li>
2016 </ul></div>
2017 </dd>
2018 <dt class="hdlist1">
2019 <code>&lt;arg-hint&gt;</code>
2020 </dt>
2021 <dd>
2022 <p>
2023         <code>&lt;arg-hint&gt;</code>, if specified, is used as a name of the argument in the
2024         help output, for options that take arguments. <code>&lt;arg-hint&gt;</code> is
2025         terminated by the first whitespace.  It is customary to use a
2026         dash to separate words in a multi-word argument hint.
2027 </p>
2028 </dd>
2029 </dl></div>
2030 <div class="paragraph"><p>The remainder of the line, after stripping the spaces, is used
2031 as the help associated to the option.</p></div>
2032 <div class="paragraph"><p>Blank lines are ignored, and lines that don&#8217;t match this specification are used
2033 as option group headers (start the line with a space to create such
2034 lines on purpose).</p></div>
2035 </div>
2036 <div class="sect2">
2037 <h3 id="_example">Example</h3>
2038 <div class="listingblock">
2039 <div class="content">
2040 <pre><code>OPTS_SPEC="\
2041 some-command [&lt;options&gt;] &lt;args&gt;...
2042
2043 some-command does foo and bar!
2044 --
2045 h,help!   show the help
2046
2047 foo       some nifty option --foo
2048 bar=      some cool option --bar with an argument
2049 baz=arg   another cool option --baz with a named argument
2050 qux?path  qux may take a path argument but has meaning by itself
2051
2052   An option group Header
2053 C?        option C with an optional argument"
2054
2055 eval "$(echo "$OPTS_SPEC" | git rev-parse --parseopt -- "$@" || echo exit $?)"</code></pre>
2056 </div></div>
2057 </div>
2058 <div class="sect2">
2059 <h3 id="_usage_text">Usage text</h3>
2060 <div class="paragraph"><p>When <code>"$@"</code> is <code>-h</code> or <code>--help</code> in the above example, the following
2061 usage text would be shown:</p></div>
2062 <div class="listingblock">
2063 <div class="content">
2064 <pre><code>usage: some-command [&lt;options&gt;] &lt;args&gt;...
2065
2066     some-command does foo and bar!
2067
2068     -h, --help            show the help
2069     --[no-]foo            some nifty option --foo
2070     --[no-]bar ...        some cool option --bar with an argument
2071     --[no-]baz &lt;arg&gt;      another cool option --baz with a named argument
2072     --[no-]qux[=&lt;path&gt;]   qux may take a path argument but has meaning by itself
2073
2074 An option group Header
2075     -C[...]               option C with an optional argument</code></pre>
2076 </div></div>
2077 </div>
2078 </div>
2079 </div>
2080 <div class="sect1">
2081 <h2 id="_sq_quote">SQ-QUOTE</h2>
2082 <div class="sectionbody">
2083 <div class="paragraph"><p>In <code>--sq-quote</code> mode, <em>git rev-parse</em> echoes on the standard output a
2084 single line suitable for <code>sh(1)</code> <code>eval</code>. This line is made by
2085 normalizing the arguments following <code>--sq-quote</code>. Nothing other than
2086 quoting the arguments is done.</p></div>
2087 <div class="paragraph"><p>If you want command input to still be interpreted as usual by
2088 <em>git rev-parse</em> before the output is shell quoted, see the <code>--sq</code>
2089 option.</p></div>
2090 <div class="sect2">
2091 <h3 id="_example_2">Example</h3>
2092 <div class="listingblock">
2093 <div class="content">
2094 <pre><code>$ cat &gt;your-git-script.sh &lt;&lt;\EOF
2095 #!/bin/sh
2096 args=$(git rev-parse --sq-quote "$@")   # quote user-supplied arguments
2097 command="git frotz -n24 $args"          # and use it inside a handcrafted
2098                                         # command line
2099 eval "$command"
2100 EOF
2101
2102 $ sh your-git-script.sh "a b'c"</code></pre>
2103 </div></div>
2104 </div>
2105 </div>
2106 </div>
2107 <div class="sect1">
2108 <h2 id="_examples">EXAMPLES</h2>
2109 <div class="sectionbody">
2110 <div class="ulist"><ul>
2111 <li>
2112 <p>
2113 Print the object name of the current commit:
2114 </p>
2115 <div class="listingblock">
2116 <div class="content">
2117 <pre><code>$ git rev-parse --verify HEAD</code></pre>
2118 </div></div>
2119 </li>
2120 <li>
2121 <p>
2122 Print the commit object name from the revision in the $REV shell variable:
2123 </p>
2124 <div class="listingblock">
2125 <div class="content">
2126 <pre><code>$ git rev-parse --verify --end-of-options $REV^{commit}</code></pre>
2127 </div></div>
2128 <div class="paragraph"><p>This will error out if $REV is empty or not a valid revision.</p></div>
2129 </li>
2130 <li>
2131 <p>
2132 Similar to above:
2133 </p>
2134 <div class="listingblock">
2135 <div class="content">
2136 <pre><code>$ git rev-parse --default master --verify --end-of-options $REV</code></pre>
2137 </div></div>
2138 <div class="paragraph"><p>but if $REV is empty, the commit object name from master will be printed.</p></div>
2139 </li>
2140 </ul></div>
2141 </div>
2142 </div>
2143 <div class="sect1">
2144 <h2 id="_git">GIT</h2>
2145 <div class="sectionbody">
2146 <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
2147 </div>
2148 </div>
2149 </div>
2150 <div id="footnotes"><hr /></div>
2151 <div id="footer">
2152 <div id="footer-text">
2153 Last updated
2154  2023-08-25 11:06:36 PDT
2155 </div>
2156 </div>
2157 </body>
2158 </html>