| blob | e791ccc40e1f40a7d7fa29aa3085ecb2af34d584 |
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>
467 useful only for <tt>HEAD</tt>, <tt>FETCH_HEAD</tt>, <tt>ORIG_HEAD</tt> and <tt>MERGE_HEAD</tt>);
468 </p>
469 </li>
470 <li>
471 <p>
473 </p>
474 </li>
475 <li>
476 <p>
478 </p>
479 </li>
480 <li>
481 <p>
483 </p>
484 </li>
485 <li>
486 <p>
488 </p>
489 </li>
490 <li>
491 <p>
493 </p>
495 FETCH_HEAD records the branch you fetched from a remote repository
497 ORIG_HEAD is created by commands that moves your HEAD in a drastic
498 way, to record the position of the HEAD before their operation, so that
499 you can change the tip of the branch back to the state before you ran
500 them easily.
501 MERGE_HEAD records the commit(s) you are merging into your branch
505 </li>
506 </ol></div>
507 </li>
508 <li>
509 <p>
511 enclosed in a brace
514 of the ref at a prior point in time. This suffix may only be
515 used immediately following a ref name and the ref must have an
520 </p>
521 </li>
522 <li>
523 <p>
529 immediately following a ref name and the ref must have an existing
531 </p>
532 </li>
533 <li>
534 <p>
536 reflog of the current branch. For example, if you are on the
538 </p>
539 </li>
540 <li>
541 <p>
543 before the current one.
544 </p>
545 </li>
546 <li>
547 <p>
549 the branch the ref is set to build on top of. Missing ref defaults
550 to the current branch.
551 </p>
552 </li>
553 <li>
554 <p>
555 A suffix <em>^</em> to a revision parameter (e.g. <em>HEAD^</em>) means the first parent of
560 object name of a tag object that refers to a commit object.
561 </p>
562 </li>
563 <li>
564 <p>
567 commit object, following only the first parent. I.e. rev~3 is
568 equivalent to rev^^^ which is equivalent to
570 the usage of this form.
571 </p>
572 </li>
573 <li>
574 <p>
577 could be a tag, and dereference the tag recursively until an
578 object of that type is found or the object cannot be
581 </p>
582 </li>
583 <li>
584 <p>
587 and dereference the tag recursively until a non-tag object is
588 found.
589 </p>
590 </li>
591 <li>
592 <p>
596 it returns the youngest matching commit which is reachable from
598 </p>
599 </li>
600 <li>
601 <p>
603 a commit whose commit message matches the specified regular expression.
604 This name returns the youngest matching commit which is
605 reachable from any ref. If the commit message starts with a
608 The regular expression can match any part of the commit message. To
610 </p>
611 </li>
612 <li>
613 <p>
615 at the given path in the tree-ish object named by the part
616 before the colon.
618 is a special case of the syntax described next: content
619 recorded in the index at the given path.
621 The given path will be converted to be relative to working tree’s root directory.
622 This is most useful to address a blob or tree from a commit or tree that has
623 the same tree structure with the working tree.
624 </p>
625 </li>
626 <li>
627 <p>
630 index at the given path. Missing stage number (and the colon
633 (typically the current branch), and stage 3 is the version from
634 the branch being merged.
635 </p>
636 </li>
637 </ul></div>
639 and C are parents of commit node A. Parent commits are ordered
640 left-to-right.</p></div>
643 <pre><tt>G H I J
644 \ / \ /
645 D E F
646 \ | / \
647 \ | / |
648 \|/ |
649 B C
650 \ /
651 \ /
652 A</tt></pre>
653 </div></div>
666 </div></div>
667 </div>
671 of commits, not just a single commit. To these commands,
672 specifying a single revision with the notation described in the
673 previous section means the set of commits reachable from that
674 commit, following the commit ancestry chain.</p></div>
680 to the syntax explained in SPECIFYING REVISIONS above), you can ask
681 for commits that are reachable from r2 excluding those that are reachable
686 It is the set of commits that are reachable from either one of
691 all of its parents.</p></div>
695 <pre><tt>D G H D
696 D F G H I J D F
697 ^G D H D
698 ^D B E I J F B
699 B...C G H D E B C
700 ^D B C E I J F B C
701 C^@ I J F
702 F^! D G H D F</tt></pre>
703 </div></div>
704 </div>
708 </div>
712 </div>
716 </div>
717 </div>
718 </body>
719 </html>