| blob | e5e9edcd760179999247f4ab6d4b2cd125289612 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 gitrevisions(7) Manual Page
407 </h1>
410 <p>gitrevisions -
411 specifying revisions and ranges for git
412 </p>
413 </div>
414 </div>
418 </div>
422 the command, they denote a specific commit or, for commands which
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
429 </div>
434 syntax. Here are various ways to spell object names. The
435 ones listed near the end of this list are to name trees and
436 blobs contained in a commit.</p></div>
438 <li>
439 <p>
440 The full SHA1 object name (40-byte hexadecimal string), or
441 a substring of such that is unique within the repository.
442 E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both
443 name the same commit object if there are no other object in
444 your repository whose object name starts with dae86e.
445 </p>
446 </li>
447 <li>
448 <p>
450 followed by a dash and a number of commits, followed by a dash, a
452 </p>
453 </li>
454 <li>
455 <p>
457 object referenced by refs/heads/master. If you
458 happen to have both heads/master and tags/master, you can
461 first match in the following rules:
462 </p>
464 <li>
465 <p>
469 </p>
470 </li>
471 <li>
472 <p>
474 </p>
475 </li>
476 <li>
477 <p>
479 </p>
480 </li>
481 <li>
482 <p>
484 </p>
485 </li>
486 <li>
487 <p>
489 </p>
490 </li>
491 <li>
492 <p>
494 </p>
496 FETCH_HEAD records the branch you fetched from a remote repository
498 ORIG_HEAD is created by commands that moves your HEAD in a drastic
499 way, to record the position of the HEAD before their operation, so that
500 you can change the tip of the branch back to the state before you ran
501 them easily.
502 MERGE_HEAD records the commit(s) you are merging into your branch
504 CHERRY_PICK_HEAD records the commit you are cherry-picking
508 </li>
509 </ol></div>
510 </li>
511 <li>
512 <p>
514 enclosed in a brace
517 of the ref at a prior point in time. This suffix may only be
518 used immediately following a ref name and the ref must have an
523 </p>
524 </li>
525 <li>
526 <p>
532 immediately following a ref name and the ref must have an existing
534 </p>
535 </li>
536 <li>
537 <p>
539 reflog of the current branch. For example, if you are on the
541 </p>
542 </li>
543 <li>
544 <p>
546 before the current one.
547 </p>
548 </li>
549 <li>
550 <p>
552 the branch the ref is set to build on top of. Missing ref defaults
553 to the current branch.
554 </p>
555 </li>
556 <li>
557 <p>
558 A suffix <em>^</em> to a revision parameter (e.g. <em>HEAD^</em>) means the first parent of
563 object name of a tag object that refers to a commit object.
564 </p>
565 </li>
566 <li>
567 <p>
570 commit object, following only the first parent. I.e. rev~3 is
571 equivalent to rev^^^ which is equivalent to
573 the usage of this form.
574 </p>
575 </li>
576 <li>
577 <p>
580 could be a tag, and dereference the tag recursively until an
581 object of that type is found or the object cannot be
584 </p>
585 </li>
586 <li>
587 <p>
590 and dereference the tag recursively until a non-tag object is
591 found.
592 </p>
593 </li>
594 <li>
595 <p>
599 it returns the youngest matching commit which is reachable from
601 </p>
602 </li>
603 <li>
604 <p>
606 a commit whose commit message matches the specified regular expression.
607 This name returns the youngest matching commit which is
608 reachable from any ref. If the commit message starts with a
611 The regular expression can match any part of the commit message. To
613 </p>
614 </li>
615 <li>
616 <p>
618 at the given path in the tree-ish object named by the part
619 before the colon.
621 is a special case of the syntax described next: content
622 recorded in the index at the given path.
624 The given path will be converted to be relative to working tree’s root directory.
625 This is most useful to address a blob or tree from a commit or tree that has
626 the same tree structure with the working tree.
627 </p>
628 </li>
629 <li>
630 <p>
633 index at the given path. Missing stage number (and the colon
636 (typically the current branch), and stage 3 is the version from
637 the branch being merged.
638 </p>
639 </li>
640 </ul></div>
642 and C are parents of commit node A. Parent commits are ordered
643 left-to-right.</p></div>
646 <pre><tt>G H I J
647 \ / \ /
648 D E F
649 \ | / \
650 \ | / |
651 \|/ |
652 B C
653 \ /
654 \ /
655 A</tt></pre>
656 </div></div>
669 </div></div>
670 </div>
674 of commits, not just a single commit. To these commands,
675 specifying a single revision with the notation described in the
676 previous section means the set of commits reachable from that
677 commit, following the commit ancestry chain.</p></div>
683 to the syntax explained in SPECIFYING REVISIONS above), you can ask
684 for commits that are reachable from r2 excluding those that are reachable
689 It is the set of commits that are reachable from either one of
694 all of its parents.</p></div>
698 <pre><tt>D G H D
699 D F G H I J D F
700 ^G D H D
701 ^D B E I J F B
702 B...C G H D E B C
703 ^D B C E I J F B C
704 C^@ I J F
705 F^! D G H D F</tt></pre>
706 </div></div>
707 </div>
711 </div>
715 </div>
719 </div>
720 </div>
721 </body>
722 </html>