| blob | 5d4db53a73e28e398349366ed9e6f7d1255fbac0 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 gitrevisions(7) Manual Page
313 </h1>
316 <p>gitrevisions -
317 specifying revisions and ranges for git
318 </p>
319 </div>
320 </div>
324 </div>
328 the command, they denote a specific commit or, for commands which
330 be reached from that commit. In the latter case one can also specify a
331 range of revisions explicitly.</p></div>
332 <div class="para"><p>In addition, some Git commands (such as <a href="git-show.html">git-show(1)</a>) also take
333 revision parameters which denote other objects than commits, e.g. blobs
335 </div>
340 syntax. Here are various ways to spell object names. The
341 ones listed near the end of this list are to name trees and
342 blobs contained in a commit.</p></div>
344 <li>
345 <p>
346 The full SHA1 object name (40-byte hexadecimal string), or
347 a substring of such that is unique within the repository.
348 E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both
349 name the same commit object if there are no other object in
350 your repository whose object name starts with dae86e.
351 </p>
352 </li>
353 <li>
354 <p>
356 followed by a dash and a number of commits, followed by a dash, a
358 </p>
359 </li>
360 <li>
361 <p>
363 object referenced by refs/heads/master. If you
364 happen to have both heads/master and tags/master, you can
367 first match in the following rules:
368 </p>
370 <li>
371 <p>
373 useful only for <tt>HEAD</tt>, <tt>FETCH_HEAD</tt>, <tt>ORIG_HEAD</tt> and <tt>MERGE_HEAD</tt>);
374 </p>
375 </li>
376 <li>
377 <p>
379 </p>
380 </li>
381 <li>
382 <p>
384 </p>
385 </li>
386 <li>
387 <p>
389 </p>
390 </li>
391 <li>
392 <p>
394 </p>
395 </li>
396 <li>
397 <p>
399 </p>
401 FETCH_HEAD records the branch you fetched from a remote repository
403 ORIG_HEAD is created by commands that moves your HEAD in a drastic
404 way, to record the position of the HEAD before their operation, so that
405 you can change the tip of the branch back to the state before you ran
406 them easily.
407 MERGE_HEAD records the commit(s) you are merging into your branch
411 </li>
412 </ol></div>
413 </li>
414 <li>
415 <p>
417 enclosed in a brace
420 of the ref at a prior point in time. This suffix may only be
421 used immediately following a ref name and the ref must have an
426 </p>
427 </li>
428 <li>
429 <p>
435 immediately following a ref name and the ref must have an existing
437 </p>
438 </li>
439 <li>
440 <p>
442 reflog of the current branch. For example, if you are on the
444 </p>
445 </li>
446 <li>
447 <p>
449 before the current one.
450 </p>
451 </li>
452 <li>
453 <p>
455 the branch the ref is set to build on top of. Missing ref defaults
456 to the current branch.
457 </p>
458 </li>
459 <li>
460 <p>
461 A suffix <em>^</em> to a revision parameter (e.g. <em>HEAD^</em>) means the first parent of
466 object name of a tag object that refers to a commit object.
467 </p>
468 </li>
469 <li>
470 <p>
473 commit object, following only the first parent. I.e. rev~3 is
474 equivalent to rev^^^ which is equivalent to
476 the usage of this form.
477 </p>
478 </li>
479 <li>
480 <p>
483 could be a tag, and dereference the tag recursively until an
484 object of that type is found or the object cannot be
487 </p>
488 </li>
489 <li>
490 <p>
493 and dereference the tag recursively until a non-tag object is
494 found.
495 </p>
496 </li>
497 <li>
498 <p>
500 a commit whose commit message matches the specified regular expression.
501 This name returns the youngest matching commit which is
502 reachable from any ref. If the commit message starts with a
505 The regular expression can match any part of the commit message. To
507 </p>
508 </li>
509 <li>
510 <p>
512 at the given path in the tree-ish object named by the part
513 before the colon.
515 is a special case of the syntax described next: content
516 recorded in the index at the given path.
517 </p>
518 </li>
519 <li>
520 <p>
523 index at the given path. Missing stage number (and the colon
526 (typically the current branch), and stage 3 is the version from
527 the branch being merged.
528 </p>
529 </li>
530 </ul></div>
532 and C are parents of commit node A. Parent commits are ordered
533 left-to-right.</p></div>
536 <pre><tt>G H I J
537 \ / \ /
538 D E F
539 \ | / \
540 \ | / |
541 \|/ |
542 B C
543 \ /
544 \ /
545 A</tt></pre>
546 </div></div>
559 </div></div>
560 </div>
564 of commits, not just a single commit. To these commands,
565 specifying a single revision with the notation described in the
566 previous section means the set of commits reachable from that
567 commit, following the commit ancestry chain.</p></div>
573 to the syntax explained in SPECIFYING REVISIONS above), you can ask
574 for commits that are reachable from r2 excluding those that are reachable
579 It is the set of commits that are reachable from either one of
584 all of its parents.</p></div>
588 <pre><tt>D G H D
589 D F G H I J D F
590 ^G D H D
591 ^D B E I J F B
592 B...C G H D E B C
593 ^D B C E I J F B C
594 C^@ I J F
595 F^! D G H D F</tt></pre>
596 </div></div>
597 </div>
601 </div>
605 </div>
609 </div>
610 </div>
611 </body>
612 </html>