gitrevisions.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
   2     "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   4 <head>
   5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
   6 <meta name="generator" content="AsciiDoc 8.4.5" />
   7 <title>gitrevisions(7)</title>
   8 <style type="text/css">
   9 /* Debug borders */
  10 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
  11 /*
  12   border: 1px solid red;
  13 */
  14 }
  15
  16 body {
  17   margin: 1em 5% 1em 5%;
  18 }
  19
  20 a {
  21   color: blue;
  22   text-decoration: underline;
  23 }
  24 a:visited {
  25   color: fuchsia;
  26 }
  27
  28 em {
  29   font-style: italic;
  30   color: navy;
  31 }
  32
  33 strong {
  34   font-weight: bold;
  35   color: #083194;
  36 }
  37
  38 tt {
  39   color: navy;
  40 }
  41
  42 h1, h2, h3, h4, h5, h6 {
  43   color: #527bbd;
  44   font-family: sans-serif;
  45   margin-top: 1.2em;
  46   margin-bottom: 0.5em;
  47   line-height: 1.3;
  48 }
  49
  50 h1, h2, h3 {
  51   border-bottom: 2px solid silver;
  52 }
  53 h2 {
  54   padding-top: 0.5em;
  55 }
  56 h3 {
  57   float: left;
  58 }
  59 h3 + * {
  60   clear: left;
  61 }
  62
  63 div.sectionbody {
  64   font-family: serif;
  65   margin-left: 0;
  66 }
  67
  68 hr {
  69   border: 1px solid silver;
  70 }
  71
  72 p {
  73   margin-top: 0.5em;
  74   margin-bottom: 0.5em;
  75 }
  76
  77 ul, ol, li > p {
  78   margin-top: 0;
  79 }
  80
  81 pre {
  82   padding: 0;
  83   margin: 0;
  84 }
  85
  86 span#author {
  87   color: #527bbd;
  88   font-family: sans-serif;
  89   font-weight: bold;
  90   font-size: 1.1em;
  91 }
  92 span#email {
  93 }
  94 span#revnumber, span#revdate, span#revremark {
  95   font-family: sans-serif;
  96 }
  97
  98 div#footer {
  99   font-family: sans-serif;
 100   font-size: small;
 101   border-top: 2px solid silver;
 102   padding-top: 0.5em;
 103   margin-top: 4.0em;
 104 }
 105 div#footer-text {
 106   float: left;
 107   padding-bottom: 0.5em;
 108 }
 109 div#footer-badges {
 110   float: right;
 111   padding-bottom: 0.5em;
 112 }
 113
 114 div#preamble {
 115   margin-top: 1.5em;
 116   margin-bottom: 1.5em;
 117 }
 118 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
 119 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 120 div.admonitionblock {
 121   margin-top: 1.5em;
 122   margin-bottom: 1.5em;
 123 }
 124 div.admonitionblock {
 125   margin-top: 2.5em;
 126   margin-bottom: 2.5em;
 127 }
 128
 129 div.content { /* Block element content. */
 130   padding: 0;
 131 }
 132
 133 /* Block element titles. */
 134 div.title, caption.title {
 135   color: #527bbd;
 136   font-family: sans-serif;
 137   font-weight: bold;
 138   text-align: left;
 139   margin-top: 1.0em;
 140   margin-bottom: 0.5em;
 141 }
 142 div.title + * {
 143   margin-top: 0;
 144 }
 145
 146 td div.title:first-child {
 147   margin-top: 0.0em;
 148 }
 149 div.content div.title:first-child {
 150   margin-top: 0.0em;
 151 }
 152 div.content + div.title {
 153   margin-top: 0.0em;
 154 }
 155
 156 div.sidebarblock > div.content {
 157   background: #ffffee;
 158   border: 1px solid silver;
 159   padding: 0.5em;
 160 }
 161
 162 div.listingblock > div.content {
 163   border: 1px solid silver;
 164   background: #f4f4f4;
 165   padding: 0.5em;
 166 }
 167
 168 div.quoteblock {
 169   padding-left: 2.0em;
 170   margin-right: 10%;
 171 }
 172 div.quoteblock > div.attribution {
 173   padding-top: 0.5em;
 174   text-align: right;
 175 }
 176
 177 div.verseblock {
 178   padding-left: 2.0em;
 179   margin-right: 10%;
 180 }
 181 div.verseblock > div.content {
 182   white-space: pre;
 183 }
 184 div.verseblock > div.attribution {
 185   padding-top: 0.75em;
 186   text-align: left;
 187 }
 188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
 189 div.verseblock + div.attribution {
 190   text-align: left;
 191 }
 192
 193 div.admonitionblock .icon {
 194   vertical-align: top;
 195   font-size: 1.1em;
 196   font-weight: bold;
 197   text-decoration: underline;
 198   color: #527bbd;
 199   padding-right: 0.5em;
 200 }
 201 div.admonitionblock td.content {
 202   padding-left: 0.5em;
 203   border-left: 2px solid silver;
 204 }
 205
 206 div.exampleblock > div.content {
 207   border-left: 2px solid silver;
 208   padding: 0.5em;
 209 }
 210
 211 div.imageblock div.content { padding-left: 0; }
 212 span.image img { border-style: none; }
 213 a.image:visited { color: white; }
 214
 215 dl {
 216   margin-top: 0.8em;
 217   margin-bottom: 0.8em;
 218 }
 219 dt {
 220   margin-top: 0.5em;
 221   margin-bottom: 0;
 222   font-style: normal;
 223   color: navy;
 224 }
 225 dd > *:first-child {
 226   margin-top: 0.1em;
 227 }
 228
 229 ul, ol {
 230     list-style-position: outside;
 231 }
 232 ol.arabic {
 233   list-style-type: decimal;
 234 }
 235 ol.loweralpha {
 236   list-style-type: lower-alpha;
 237 }
 238 ol.upperalpha {
 239   list-style-type: upper-alpha;
 240 }
 241 ol.lowerroman {
 242   list-style-type: lower-roman;
 243 }
 244 ol.upperroman {
 245   list-style-type: upper-roman;
 246 }
 247
 248 div.compact ul, div.compact ol,
 249 div.compact p, div.compact p,
 250 div.compact div, div.compact div {
 251   margin-top: 0.1em;
 252   margin-bottom: 0.1em;
 253 }
 254
 255 div.tableblock > table {
 256   border: 3px solid #527bbd;
 257 }
 258 thead {
 259   font-family: sans-serif;
 260   font-weight: bold;
 261 }
 262 tfoot {
 263   font-weight: bold;
 264 }
 265 td > div.verse {
 266   white-space: pre;
 267 }
 268 p.table {
 269   margin-top: 0;
 270 }
 271 /* Because the table frame attribute is overriden by CSS in most browsers. */
 272 div.tableblock > table[frame="void"] {
 273   border-style: none;
 274 }
 275 div.tableblock > table[frame="hsides"] {
 276   border-left-style: none;
 277   border-right-style: none;
 278 }
 279 div.tableblock > table[frame="vsides"] {
 280   border-top-style: none;
 281   border-bottom-style: none;
 282 }
 283
 284
 285 div.hdlist {
 286   margin-top: 0.8em;
 287   margin-bottom: 0.8em;
 288 }
 289 div.hdlist tr {
 290   padding-bottom: 15px;
 291 }
 292 dt.hdlist1.strong, td.hdlist1.strong {
 293   font-weight: bold;
 294 }
 295 td.hdlist1 {
 296   vertical-align: top;
 297   font-style: normal;
 298   padding-right: 0.8em;
 299   color: navy;
 300 }
 301 td.hdlist2 {
 302   vertical-align: top;
 303 }
 304 div.hdlist.compact tr {
 305   margin: 0;
 306   padding-bottom: 0;
 307 }
 308
 309 .comment {
 310   background: yellow;
 311 }
 312
 313 @media print {
 314   div#footer-badges { display: none; }
 315 }
 316
 317 div#toctitle {
 318   color: #527bbd;
 319   font-family: sans-serif;
 320   font-size: 1.1em;
 321   font-weight: bold;
 322   margin-top: 1.0em;
 323   margin-bottom: 0.1em;
 324 }
 325
 326 div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
 327   margin-top: 0;
 328   margin-bottom: 0;
 329 }
 330 div.toclevel2 {
 331   margin-left: 2em;
 332   font-size: 0.9em;
 333 }
 334 div.toclevel3 {
 335   margin-left: 4em;
 336   font-size: 0.9em;
 337 }
 338 div.toclevel4 {
 339   margin-left: 6em;
 340   font-size: 0.9em;
 341 }
 342 /* Overrides for manpage documents */
 343 h1 {
 344   padding-top: 0.5em;
 345   padding-bottom: 0.5em;
 346   border-top: 2px solid silver;
 347   border-bottom: 2px solid silver;
 348 }
 349 h2 {
 350   border-style: none;
 351 }
 352 div.sectionbody {
 353   margin-left: 5%;
 354 }
 355
 356 @media print {
 357   div#toc { display: none; }
 358 }
 359
 360 /* Workarounds for IE6's broken and incomplete CSS2. */
 361
 362 div.sidebar-content {
 363   background: #ffffee;
 364   border: 1px solid silver;
 365   padding: 0.5em;
 366 }
 367 div.sidebar-title, div.image-title {
 368   color: #527bbd;
 369   font-family: sans-serif;
 370   font-weight: bold;
 371   margin-top: 0.0em;
 372   margin-bottom: 0.5em;
 373 }
 374
 375 div.listingblock div.content {
 376   border: 1px solid silver;
 377   background: #f4f4f4;
 378   padding: 0.5em;
 379 }
 380
 381 div.quoteblock-attribution {
 382   padding-top: 0.5em;
 383   text-align: right;
 384 }
 385
 386 div.verseblock-content {
 387   white-space: pre;
 388 }
 389 div.verseblock-attribution {
 390   padding-top: 0.75em;
 391   text-align: left;
 392 }
 393
 394 div.exampleblock-content {
 395   border-left: 2px solid silver;
 396   padding-left: 0.5em;
 397 }
 398
 399 /* IE6 sets dynamically generated links as visited. */
 400 div#toc a:visited { color: blue; }
 401 </style>
 402 </head>
 403 <body>
 404 <div id="header">
 405 <h1>
 406 gitrevisions(7) Manual Page
 407 </h1>
 408 <h2>NAME</h2>
 409 <div class="sectionbody">
 410 <p>gitrevisions -
 411    specifying revisions and ranges for git
 412 </p>
 413 </div>
 414 </div>
 415 <h2 id="_synopsis">SYNOPSIS</h2>
 416 <div class="sectionbody">
 417 <div class="paragraph"><p>gitrevisions</p></div>
 418 </div>
 419 <h2 id="_description">DESCRIPTION</h2>
 420 <div class="sectionbody">
 421 <div class="paragraph"><p>Many Git commands take revision parameters as arguments. Depending on
 422 the command, they denote a specific commit or, for commands which
 423 walk the revision graph (such as <a href="git-log.html">git-log(1)</a>), all commits which can
 424 be reached from that commit. In the latter case one can also specify a
 425 range of revisions explicitly.</p></div>
 426 <div class="paragraph"><p>In addition, some Git commands (such as <a href="git-show.html">git-show(1)</a>) also take
 427 revision parameters which denote other objects than commits, e.g. blobs
 428 ("files") or trees ("directories of files").</p></div>
 429 </div>
 430 <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
 431 <div class="sectionbody">
 432 <div class="paragraph"><p>A revision parameter <em>&lt;rev&gt;</em> typically, but not necessarily, names a
 433 commit object.  It uses what is called an <em>extended SHA1</em>
 434 syntax.  Here are various ways to spell object names.  The
 435 ones listed near the end of this list name trees and
 436 blobs contained in a commit.</p></div>
 437 <div class="dlist"><dl>
 438 <dt class="hdlist1">
 439 <em>&lt;sha1&gt;</em>, e.g. <em>dae86e1950b1277e545cee180551750029cfe735</em>, <em>dae86e</em>
 440 </dt>
 441 <dd>
 442 <p>
 443   The full SHA1 object name (40-byte hexadecimal string), or
 444   a leading substring that is unique within the repository.
 445   E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both
 446   name the same commit object if there is no other object in
 447   your repository whose object name starts with dae86e.
 448 </p>
 449 </dd>
 450 <dt class="hdlist1">
 451 <em>&lt;describeOutput&gt;</em>, e.g. <em>v1.7.4.2-679-g3bee7fb</em>
 452 </dt>
 453 <dd>
 454 <p>
 455   Output from <tt>git describe</tt>; i.e. a closest tag, optionally
 456   followed by a dash and a number of commits, followed by a dash, a
 457   <em>g</em>, and an abbreviated object name.
 458 </p>
 459 </dd>
 460 <dt class="hdlist1">
 461 <em>&lt;refname&gt;</em>, e.g. <em>master</em>, <em>heads/master</em>, <em>refs/heads/master</em>
 462 </dt>
 463 <dd>
 464 <p>
 465   A symbolic ref name.  E.g. <em>master</em> typically means the commit
 466   object referenced by <em>refs/heads/master</em>.  If you
 467   happen to have both <em>heads/master</em> and <em>tags/master</em>, you can
 468   explicitly say <em>heads/master</em> to tell git which one you mean.
 469   When ambiguous, a <em>&lt;name&gt;</em> is disambiguated by taking the
 470   first match in the following rules:
 471 </p>
 472 <div class="olist arabic"><ol class="arabic">
 473 <li>
 474 <p>
 475 If <em>$GIT_DIR/&lt;name&gt;</em> exists, that is what you mean (this is usually
 476     useful only for <em>HEAD</em>, <em>FETCH_HEAD</em>, <em>ORIG_HEAD</em>, <em>MERGE_HEAD</em>
 477     and <em>CHERRY_PICK_HEAD</em>);
 478 </p>
 479 </li>
 480 <li>
 481 <p>
 482 otherwise, <em>refs/&lt;name&gt;</em> if it exists;
 483 </p>
 484 </li>
 485 <li>
 486 <p>
 487 otherwise, <em>refs/tags/&lt;refname&gt;</em> if it exists;
 488 </p>
 489 </li>
 490 <li>
 491 <p>
 492 otherwise, <em>refs/heads/&lt;name&gt;</em> if it exists;
 493 </p>
 494 </li>
 495 <li>
 496 <p>
 497 otherwise, <em>refs/remotes/&lt;name&gt;</em> if it exists;
 498 </p>
 499 </li>
 500 <li>
 501 <p>
 502 otherwise, <em>refs/remotes/&lt;name&gt;/HEAD</em> if it exists.
 503 </p>
 504 <div class="paragraph"><p><em>HEAD</em> names the commit on which you based the changes in the working tree.
 505 <em>FETCH_HEAD</em> records the branch which you fetched from a remote repository
 506 with your last <tt>git fetch</tt> invocation.
 507 <em>ORIG_HEAD</em> is created by commands that move your <em>HEAD</em> in a drastic
 508 way, to record the position of the <em>HEAD</em> before their operation, so that
 509 you can easily change the tip of the branch back to the state before you ran
 510 them.
 511 <em>MERGE_HEAD</em> records the commit(s) which you are merging into your branch
 512 when you run <tt>git merge</tt>.
 513 <em>CHERRY_PICK_HEAD</em> records the commit which you are cherry-picking
 514 when you run <tt>git cherry-pick</tt>.</p></div>
 515 <div class="paragraph"><p>Note that any of the <em>refs/*</em> cases above may come either from
 516 the <em>$GIT_DIR/refs</em> directory or from the <em>$GIT_DIR/packed-refs</em> file.</p></div>
 517 </li>
 518 </ol></div>
 519 </dd>
 520 <dt class="hdlist1">
 521 <em>&lt;refname&gt;@{&lt;date&gt;}</em>, e.g. <em>master@{yesterday}</em>, <em>HEAD@{5 minutes ago}</em>
 522 </dt>
 523 <dd>
 524 <p>
 525   A ref followed by the suffix <em>@</em> with a date specification
 526   enclosed in a brace
 527   pair (e.g. <em>{yesterday}</em>, <em>{1 month 2 weeks 3 days 1 hour 1
 528   second ago}</em> or <em>{1979-02-26 18:30:00}</em>) specifies the value
 529   of the ref at a prior point in time.  This suffix may only be
 530   used immediately following a ref name and the ref must have an
 531   existing log (<em>$GIT_DIR/logs/&lt;ref&gt;</em>). Note that this looks up the state
 532   of your <strong>local</strong> ref at a given time; e.g., what was in your local
 533   <em>master</em> branch last week. If you want to look at commits made during
 534   certain times, see <em>--since</em> and <em>--until</em>.
 535 </p>
 536 </dd>
 537 <dt class="hdlist1">
 538 <em>&lt;refname&gt;@{&lt;n&gt;}</em>, e.g. <em>master@{1}</em>
 539 </dt>
 540 <dd>
 541 <p>
 542   A ref followed by the suffix <em>@</em> with an ordinal specification
 543   enclosed in a brace pair (e.g. <em>{1}</em>, <em>{15}</em>) specifies
 544   the n-th prior value of that ref.  For example <em>master@{1}</em>
 545   is the immediate prior value of <em>master</em> while <em>master@{5}</em>
 546   is the 5th prior value of <em>master</em>. This suffix may only be used
 547   immediately following a ref name and the ref must have an existing
 548   log (<em>$GIT_DIR/logs/&lt;refname&gt;</em>).
 549 </p>
 550 </dd>
 551 <dt class="hdlist1">
 552 <em>@{&lt;n&gt;}</em>, e.g. <em>@{1}</em>
 553 </dt>
 554 <dd>
 555 <p>
 556   You can use the <em>@</em> construct with an empty ref part to get at a
 557   reflog entry of the current branch. For example, if you are on
 558   branch <em>blabla</em> then <em>@{1}</em> means the same as <em>blabla@{1}</em>.
 559 </p>
 560 </dd>
 561 <dt class="hdlist1">
 562 <em>@{-&lt;n&gt;}</em>, e.g. <em>@{-1}</em>
 563 </dt>
 564 <dd>
 565 <p>
 566   The construct <em>@{-&lt;n&gt;}</em> means the &lt;n&gt;th branch checked out
 567   before the current one.
 568 </p>
 569 </dd>
 570 <dt class="hdlist1">
 571 <em>&lt;refname&gt;@{upstream}</em>, e.g. <em>master@{upstream}</em>, <em>@{u}</em>
 572 </dt>
 573 <dd>
 574 <p>
 575   The suffix <em>@{upstream}</em> to a ref (short form <em>&lt;refname&gt;@{u}</em>) refers to
 576   the branch the ref is set to build on top of.  A missing ref defaults
 577   to the current branch.
 578 </p>
 579 </dd>
 580 <dt class="hdlist1">
 581 <em>&lt;rev&gt;&#94;</em>, e.g. <em>HEAD&#94;, v1.5.1&#94;0</em>
 582 </dt>
 583 <dd>
 584 <p>
 585   A suffix <em>&#94;</em> to a revision parameter means the first parent of
 586   that commit object.  <em>&#94;&lt;n&gt;</em> means the &lt;n&gt;th parent (i.e.
 587   <em>&lt;rev&gt;&#94;</em>
 588   is equivalent to <em>&lt;rev&gt;&#94;1</em>).  As a special rule,
 589   <em>&lt;rev&gt;&#94;0</em> means the commit itself and is used when <em>&lt;rev&gt;</em> is the
 590   object name of a tag object that refers to a commit object.
 591 </p>
 592 </dd>
 593 <dt class="hdlist1">
 594 <em>&lt;rev&gt;&#126;&lt;n&gt;</em>, e.g. <em>master&#126;3</em>
 595 </dt>
 596 <dd>
 597 <p>
 598   A suffix <em>&#126;&lt;n&gt;</em> to a revision parameter means the commit
 599   object that is the &lt;n&gt;th generation grand-parent of the named
 600   commit object, following only the first parents.  I.e. <em>&lt;rev&gt;&#126;3</em> is
 601   equivalent to <em>&lt;rev&gt;&#94;&#94;&#94;</em> which is equivalent to
 602   <em>&lt;rev&gt;&#94;1&#94;1&#94;1</em>.  See below for an illustration of
 603   the usage of this form.
 604 </p>
 605 </dd>
 606 <dt class="hdlist1">
 607 <em>&lt;rev&gt;&#94;{&lt;type&gt;}</em>, e.g. <em>v0.99.8&#94;{commit}</em>
 608 </dt>
 609 <dd>
 610 <p>
 611   A suffix <em>&#94;</em> followed by an object type name enclosed in
 612   brace pair means the object
 613   could be a tag, and dereference the tag recursively until an
 614   object of that type is found or the object cannot be
 615   dereferenced anymore (in which case, barf).  <em>&lt;rev&gt;&#94;0</em>
 616   is a short-hand for <em>&lt;rev&gt;&#94;{commit}</em>.
 617 </p>
 618 </dd>
 619 <dt class="hdlist1">
 620 <em>&lt;rev&gt;&#94;{}</em>, e.g. <em>v0.99.8&#94;{}</em>
 621 </dt>
 622 <dd>
 623 <p>
 624   A suffix <em>&#94;</em> followed by an empty brace pair
 625   means the object could be a tag,
 626   and dereference the tag recursively until a non-tag object is
 627   found.
 628 </p>
 629 </dd>
 630 <dt class="hdlist1">
 631 <em>&lt;rev&gt;&#94;{/&lt;text&gt;}</em>, e.g. <em>HEAD^{/fix nasty bug}</em>
 632 </dt>
 633 <dd>
 634 <p>
 635   A suffix <em>&#94;</em> to a revision parameter, followed by a brace
 636   pair that contains a text led by a slash,
 637   is the same as the <em>:/fix nasty bug</em> syntax below except that
 638   it returns the youngest matching commit which is reachable from
 639   the <em>&lt;rev&gt;</em> before <em>&#94;</em>.
 640 </p>
 641 </dd>
 642 <dt class="hdlist1">
 643 <em>:/&lt;text&gt;</em>, e.g. <em>:/fix nasty bug</em>
 644 </dt>
 645 <dd>
 646 <p>
 647   A colon, followed by a slash, followed by a text, names
 648   a commit whose commit message matches the specified regular expression.
 649   This name returns the youngest matching commit which is
 650   reachable from any ref.  If the commit message starts with a
 651   <em>!</em> you have to repeat that;  the special sequence <em>:/!</em>,
 652   followed by something else than <em>!</em>, is reserved for now.
 653   The regular expression can match any part of the commit message. To
 654   match messages starting with a string, one can use e.g. <em>:/^foo</em>.
 655 </p>
 656 </dd>
 657 <dt class="hdlist1">
 658 <em>&lt;rev&gt;:&lt;path&gt;</em>, e.g. <em>HEAD:README</em>, <em>:README</em>, <em>master:./README</em>
 659 </dt>
 660 <dd>
 661 <p>
 662   A suffix <em>:</em> followed by a path names the blob or tree
 663   at the given path in the tree-ish object named by the part
 664   before the colon.
 665   <em>:path</em> (with an empty part before the colon)
 666   is a special case of the syntax described next: content
 667   recorded in the index at the given path.
 668   A path starting with <em>./</em> or <em>../</em> is relative to the current working directory.
 669   The given path will be converted to be relative to the working tree&#8217;s root directory.
 670   This is most useful to address a blob or tree from a commit or tree that has
 671   the same tree structure as the working tree.
 672 </p>
 673 </dd>
 674 <dt class="hdlist1">
 675 <em>:&lt;n&gt;:&lt;path&gt;</em>, e.g. <em>:0:README</em>, <em>:README</em>
 676 </dt>
 677 <dd>
 678 <p>
 679   A colon, optionally followed by a stage number (0 to 3) and a
 680   colon, followed by a path, names a blob object in the
 681   index at the given path. A missing stage number (and the colon
 682   that follows it) names a stage 0 entry. During a merge, stage
 683   1 is the common ancestor, stage 2 is the target branch&#8217;s version
 684   (typically the current branch), and stage 3 is the version from
 685   the branch which is being merged.
 686 </p>
 687 </dd>
 688 </dl></div>
 689 <div class="paragraph"><p>Here is an illustration, by Jon Loeliger.  Both commit nodes B
 690 and C are parents of commit node A.  Parent commits are ordered
 691 left-to-right.</p></div>
 692 <div class="literalblock">
 693 <div class="content">
 694 <pre><tt>G   H   I   J
 695  \ /     \ /
 696   D   E   F
 697    \  |  / \
 698     \ | /   |
 699      \|/    |
 700       B     C
 701        \   /
 702         \ /
 703          A</tt></pre>
 704 </div></div>
 705 <div class="literalblock">
 706 <div class="content">
 707 <pre><tt>A =      = A^0
 708 B = A^   = A^1     = A~1
 709 C = A^2  = A^2
 710 D = A^^  = A^1^1   = A~2
 711 E = B^2  = A^^2
 712 F = B^3  = A^^3
 713 G = A^^^ = A^1^1^1 = A~3
 714 H = D^2  = B^^2    = A^^^2  = A~2^2
 715 I = F^   = B^3^    = A^^3^
 716 J = F^2  = B^3^2   = A^^3^2</tt></pre>
 717 </div></div>
 718 </div>
 719 <h2 id="_specifying_ranges">SPECIFYING RANGES</h2>
 720 <div class="sectionbody">
 721 <div class="paragraph"><p>History traversing commands such as <tt>git log</tt> operate on a set
 722 of commits, not just a single commit.  To these commands,
 723 specifying a single revision with the notation described in the
 724 previous section means the set of commits reachable from that
 725 commit, following the commit ancestry chain.</p></div>
 726 <div class="paragraph"><p>To exclude commits reachable from a commit, a prefix <em>&#94;</em>
 727 notation is used.  E.g. <em>&#94;r1 r2</em> means commits reachable
 728 from <em>r2</em> but exclude the ones reachable from <em>r1</em>.</p></div>
 729 <div class="paragraph"><p>This set operation appears so often that there is a shorthand
 730 for it.  When you have two commits <em>r1</em> and <em>r2</em> (named according
 731 to the syntax explained in SPECIFYING REVISIONS above), you can ask
 732 for commits that are reachable from r2 excluding those that are reachable
 733 from r1 by <em>&#94;r1 r2</em> and it can be written as <em>r1..r2</em>.</p></div>
 734 <div class="paragraph"><p>A similar notation <em>r1...r2</em> is called symmetric difference
 735 of <em>r1</em> and <em>r2</em> and is defined as
 736 <em>r1 r2 --not $(git merge-base --all r1 r2)</em>.
 737 It is the set of commits that are reachable from either one of
 738 <em>r1</em> or <em>r2</em> but not from both.</p></div>
 739 <div class="paragraph"><p>Two other shorthands for naming a set that is formed by a commit
 740 and its parent commits exist.  The <em>r1&#94;@</em> notation means all
 741 parents of <em>r1</em>.  <em>r1&#94;!</em> includes commit <em>r1</em> but excludes
 742 all of its parents.</p></div>
 743 <div class="paragraph"><p>Here are a handful of examples:</p></div>
 744 <div class="literalblock">
 745 <div class="content">
 746 <pre><tt>D                G H D
 747 D F              G H I J D F
 748 ^G D             H D
 749 ^D B             E I J F B
 750 B...C            G H D E B C
 751 ^D B C           E I J F B C
 752 C^@              I J F
 753 F^! D            G H D F</tt></pre>
 754 </div></div>
 755 </div>
 756 <h2 id="_see_also">SEE ALSO</h2>
 757 <div class="sectionbody">
 758 <div class="paragraph"><p><a href="git-rev-parse.html">git-rev-parse(1)</a></p></div>
 759 </div>
 760 <h2 id="_git">GIT</h2>
 761 <div class="sectionbody">
 762 <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
 763 </div>
 764 <div id="footer">
 765 <div id="footer-text">
 766 Last updated 2010-07-15 22:23:57 UTC
 767 </div>
 768 </div>
 769 </body>
 770 </html>