| blob | 9d1f3d0b5984e06d33628c8ead89d18469f9ab76 |
1 '\" t
2 .\" Title: gitrevisions
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets v1.79.2 <http://docbook.sf.net/>
5 .\" Date: 2024-09-20
6 .\" Manual: Git Manual
7 .\" Source: Git 2.46.1.603.g94b60adee3
8 .\" Language: English
9 .\"
10 .TH "GITREVISIONS" "7" "2024-09-20" "Git 2\&.46\&.1\&.603\&.g94b60a" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 .ie \n(.g .ds Aq \(aq
19 .el .ds Aq '
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
24 .nh
25 .\" disable justification (adjust text to left margin only)
26 .ad l
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
30 .SH "NAME"
31 gitrevisions \- Specifying revisions and ranges for Git
32 .SH "SYNOPSIS"
33 .sp
34 gitrevisions
35 .SH "DESCRIPTION"
36 .sp
37 Many Git commands take revision parameters as arguments\&. Depending on the command, they denote a specific commit or, for commands which walk the revision graph (such as \fBgit-log\fR(1)), all commits which are reachable from that commit\&. For commands that walk the revision graph one can also specify a range of revisions explicitly\&.
38 .sp
39 In addition, some Git commands (such as \fBgit-show\fR(1) and \fBgit-push\fR(1)) can also take revision parameters which denote other objects than commits, e\&.g\&. blobs ("files") or trees ("directories of files")\&.
40 .SH "SPECIFYING REVISIONS"
41 .sp
42 A revision parameter \fI<rev>\fR typically, but not necessarily, names a commit object\&. It uses what is called an \fIextended SHA\-1\fR syntax\&. Here are various ways to spell object names\&. The ones listed near the end of this list name trees and blobs contained in a commit\&.
43 .if n \{\
44 .sp
45 .\}
46 .RS 4
47 .it 1 an-trap
48 .nr an-no-space-flag 1
49 .nr an-break-flag 1
50 .br
51 .ps +1
52 \fBNote\fR
53 .ps -1
54 .br
55 .sp
56 This document shows the "raw" syntax as seen by git\&. The shell and other UIs might require additional quoting to protect special characters and to avoid word splitting\&.
57 .sp .5v
58 .RE
59 .PP
60 \fI<sha1>\fR, e\&.g\&. \fIdae86e1950b1277e545cee180551750029cfe735\fR, \fIdae86e\fR
61 .RS 4
62 The full SHA\-1 object name (40\-byte hexadecimal string), or a leading substring that is unique within the repository\&. E\&.g\&. dae86e1950b1277e545cee180551750029cfe735 and dae86e both name the same commit object if there is no other object in your repository whose object name starts with dae86e\&.
63 .RE
64 .PP
65 \fI<describeOutput>\fR, e\&.g\&. \fIv1\&.7\&.4\&.2\-679\-g3bee7fb\fR
66 .RS 4
67 Output from
68 \fBgit describe\fR; i\&.e\&. a closest tag, optionally followed by a dash and a number of commits, followed by a dash, a
69 \fIg\fR, and an abbreviated object name\&.
70 .RE
71 .PP
72 \fI<refname>\fR, e\&.g\&. \fImaster\fR, \fIheads/master\fR, \fIrefs/heads/master\fR
73 .RS 4
74 A symbolic ref name\&. E\&.g\&.
75 \fImaster\fR
76 typically means the commit object referenced by
77 \fIrefs/heads/master\fR\&. If you happen to have both
78 \fIheads/master\fR
79 and
80 \fItags/master\fR, you can explicitly say
81 \fIheads/master\fR
82 to tell Git which one you mean\&. When ambiguous, a
83 \fI<refname>\fR
84 is disambiguated by taking the first match in the following rules:
85 .sp
86 .RS 4
87 .ie n \{\
88 \h'-04' 1.\h'+01'\c
89 .\}
90 .el \{\
91 .sp -1
92 .IP " 1." 4.2
93 .\}
94 If
95 \fI$GIT_DIR/<refname>\fR
96 exists, that is what you mean (this is usually useful only for
97 \fBHEAD\fR,
98 \fBFETCH_HEAD\fR,
99 \fBORIG_HEAD\fR,
100 \fBMERGE_HEAD\fR,
101 \fBREBASE_HEAD\fR,
102 \fBREVERT_HEAD\fR,
103 \fBCHERRY_PICK_HEAD\fR,
104 \fBBISECT_HEAD\fR
105 and
106 \fBAUTO_MERGE\fR);
107 .RE
108 .sp
109 .RS 4
110 .ie n \{\
111 \h'-04' 2.\h'+01'\c
112 .\}
113 .el \{\
114 .sp -1
115 .IP " 2." 4.2
116 .\}
117 otherwise,
118 \fIrefs/<refname>\fR
119 if it exists;
120 .RE
121 .sp
122 .RS 4
123 .ie n \{\
124 \h'-04' 3.\h'+01'\c
125 .\}
126 .el \{\
127 .sp -1
128 .IP " 3." 4.2
129 .\}
130 otherwise,
131 \fIrefs/tags/<refname>\fR
132 if it exists;
133 .RE
134 .sp
135 .RS 4
136 .ie n \{\
137 \h'-04' 4.\h'+01'\c
138 .\}
139 .el \{\
140 .sp -1
141 .IP " 4." 4.2
142 .\}
143 otherwise,
144 \fIrefs/heads/<refname>\fR
145 if it exists;
146 .RE
147 .sp
148 .RS 4
149 .ie n \{\
150 \h'-04' 5.\h'+01'\c
151 .\}
152 .el \{\
153 .sp -1
154 .IP " 5." 4.2
155 .\}
156 otherwise,
157 \fIrefs/remotes/<refname>\fR
158 if it exists;
159 .RE
160 .sp
161 .RS 4
162 .ie n \{\
163 \h'-04' 6.\h'+01'\c
164 .\}
165 .el \{\
166 .sp -1
167 .IP " 6." 4.2
168 .\}
169 otherwise,
170 \fIrefs/remotes/<refname>/HEAD\fR
171 if it exists\&.
172 .PP
173 \fBHEAD\fR
174 .RS 4
175 names the commit on which you based the changes in the working tree\&.
176 .RE
177 .PP
178 \fBFETCH_HEAD\fR
179 .RS 4
180 records the branch which you fetched from a remote repository with your last
181 \fBgit fetch\fR
182 invocation\&.
183 .RE
184 .PP
185 \fBORIG_HEAD\fR
186 .RS 4
187 is created by commands that move your
188 \fBHEAD\fR
189 in a drastic way (\fBgit am\fR,
190 \fBgit merge\fR,
191 \fBgit rebase\fR,
192 \fBgit reset\fR), to record the position of the
193 \fBHEAD\fR
194 before their operation, so that you can easily change the tip of the branch back to the state before you ran them\&.
195 .RE
196 .PP
197 \fBMERGE_HEAD\fR
198 .RS 4
199 records the commit(s) which you are merging into your branch when you run
200 \fBgit merge\fR\&.
201 .RE
202 .PP
203 \fBREBASE_HEAD\fR
204 .RS 4
205 during a rebase, records the commit at which the operation is currently stopped, either because of conflicts or an
206 \fBedit\fR
207 command in an interactive rebase\&.
208 .RE
209 .PP
210 \fBREVERT_HEAD\fR
211 .RS 4
212 records the commit which you are reverting when you run
213 \fBgit revert\fR\&.
214 .RE
215 .PP
216 \fBCHERRY_PICK_HEAD\fR
217 .RS 4
218 records the commit which you are cherry\-picking when you run
219 \fBgit cherry\-pick\fR\&.
220 .RE
221 .PP
222 \fBBISECT_HEAD\fR
223 .RS 4
224 records the current commit to be tested when you run
225 \fBgit bisect \-\-no\-checkout\fR\&.
226 .RE
227 .PP
228 \fBAUTO_MERGE\fR
229 .RS 4
230 records a tree object corresponding to the state the
231 \fIort\fR
232 merge strategy wrote to the working tree when a merge operation resulted in conflicts\&.
233 .RE
234 .RE
235 .sp
236 Note that any of the
237 \fIrefs/*\fR
238 cases above may come either from the
239 \fB$GIT_DIR/refs\fR
240 directory or from the
241 \fB$GIT_DIR/packed\-refs\fR
242 file\&. While the ref name encoding is unspecified, UTF\-8 is preferred as some output processing may assume ref names in UTF\-8\&.
243 .RE
244 .PP
245 \fI@\fR
246 .RS 4
247 \fI@\fR
248 alone is a shortcut for
249 \fBHEAD\fR\&.
250 .RE
251 .PP
252 \fI[<refname>]@{<date>}\fR, e\&.g\&. \fImaster@{yesterday}\fR, \fIHEAD@{5 minutes ago}\fR
253 .RS 4
254 A ref followed by the suffix
255 \fI@\fR
256 with a date specification enclosed in a brace pair (e\&.g\&.
257 \fI{yesterday}\fR,
258 \fI{1 month 2 weeks 3 days 1 hour 1 second ago}\fR
259 or
260 \fI{1979\-02\-26 18:30:00}\fR) specifies the value of the ref at a prior point in time\&. This suffix may only be used immediately following a ref name and the ref must have an existing log (\fI$GIT_DIR/logs/<ref>\fR)\&. Note that this looks up the state of your
261 \fBlocal\fR
262 ref at a given time; e\&.g\&., what was in your local
263 \fImaster\fR
264 branch last week\&. If you want to look at commits made during certain times, see
265 \fB\-\-since\fR
266 and
267 \fB\-\-until\fR\&.
268 .RE
269 .PP
270 \fI<refname>@{<n>}\fR, e\&.g\&. \fImaster@{1}\fR
271 .RS 4
272 A ref followed by the suffix
273 \fI@\fR
274 with an ordinal specification enclosed in a brace pair (e\&.g\&.
275 \fI{1}\fR,
276 \fI{15}\fR) specifies the n\-th prior value of that ref\&. For example
277 \fImaster@{1}\fR
278 is the immediate prior value of
279 \fImaster\fR
280 while
281 \fImaster@{5}\fR
282 is the 5th prior value of
283 \fImaster\fR\&. This suffix may only be used immediately following a ref name and the ref must have an existing log (\fI$GIT_DIR/logs/<refname>\fR)\&.
284 .RE
285 .PP
286 \fI@{<n>}\fR, e\&.g\&. \fI@{1}\fR
287 .RS 4
288 You can use the
289 \fI@\fR
290 construct with an empty ref part to get at a reflog entry of the current branch\&. For example, if you are on branch
291 \fIblabla\fR
292 then
293 \fI@{1}\fR
294 means the same as
295 \fIblabla@{1}\fR\&.
296 .RE
297 .PP
298 \fI@{\-<n>}\fR, e\&.g\&. \fI@{\-1}\fR
299 .RS 4
300 The construct
301 \fI@{\-<n>}\fR
302 means the <n>th branch/commit checked out before the current one\&.
303 .RE
304 .PP
305 \fI[<branchname>]@{upstream}\fR, e\&.g\&. \fImaster@{upstream}\fR, \fI@{u}\fR
306 .RS 4
307 A branch B may be set up to build on top of a branch X (configured with
308 \fBbranch\&.<name>\&.merge\fR) at a remote R (configured with
309 \fBbranch\&.<name>\&.remote\fR)\&. B@{u} refers to the remote\-tracking branch for the branch X taken from remote R, typically found at
310 \fBrefs/remotes/R/X\fR\&.
311 .RE
312 .PP
313 \fI[<branchname>]@{push}\fR, e\&.g\&. \fImaster@{push}\fR, \fI@{push}\fR
314 .RS 4
315 The suffix
316 \fI@{push}\fR
317 reports the branch "where we would push to" if
318 \fBgit push\fR
319 were run while
320 \fBbranchname\fR
321 was checked out (or the current
322 \fBHEAD\fR
323 if no branchname is specified)\&. Like for
324 \fI@{upstream}\fR, we report the remote\-tracking branch that corresponds to that branch at the remote\&.
325 .sp
326 Here\(cqs an example to make it more clear:
327 .sp
328 .if n \{\
329 .RS 4
330 .\}
331 .nf
332 $ git config push\&.default current
333 $ git config remote\&.pushdefault myfork
334 $ git switch \-c mybranch origin/master
336 $ git rev\-parse \-\-symbolic\-full\-name @{upstream}
337 refs/remotes/origin/master
339 $ git rev\-parse \-\-symbolic\-full\-name @{push}
340 refs/remotes/myfork/mybranch
341 .fi
342 .if n \{\
343 .RE
344 .\}
345 .sp
346 Note in the example that we set up a triangular workflow, where we pull from one location and push to another\&. In a non\-triangular workflow,
347 \fI@{push}\fR
348 is the same as
349 \fI@{upstream}\fR, and there is no need for it\&.
350 .sp
351 This suffix is also accepted when spelled in uppercase, and means the same thing no matter the case\&.
352 .RE
353 .PP
354 \fI<rev>^[<n>]\fR, e\&.g\&. \fIHEAD^, v1\&.5\&.1^0\fR
355 .RS 4
356 A suffix
357 \fI^\fR
358 to a revision parameter means the first parent of that commit object\&.
359 \fI^<n>\fR
360 means the <n>th parent (i\&.e\&.
361 \fI<rev>^\fR
362 is equivalent to
363 \fI<rev>^1\fR)\&. As a special rule,
364 \fI<rev>^0\fR
365 means the commit itself and is used when
366 \fI<rev>\fR
367 is the object name of a tag object that refers to a commit object\&.
368 .RE
369 .PP
370 \fI<rev>~[<n>]\fR, e\&.g\&. \fIHEAD~, master~3\fR
371 .RS 4
372 A suffix
373 \fI~\fR
374 to a revision parameter means the first parent of that commit object\&. A suffix
375 \fI~<n>\fR
376 to a revision parameter means the commit object that is the <n>th generation ancestor of the named commit object, following only the first parents\&. I\&.e\&.
377 \fI<rev>~3\fR
378 is equivalent to
379 \fI<rev>^^^\fR
380 which is equivalent to
381 \fI<rev>^1^1^1\fR\&. See below for an illustration of the usage of this form\&.
382 .RE
383 .PP
384 \fI<rev>^{<type>}\fR, e\&.g\&. \fIv0\&.99\&.8^{commit}\fR
385 .RS 4
386 A suffix
387 \fI^\fR
388 followed by an object type name enclosed in brace pair means dereference the object at
389 \fI<rev>\fR
390 recursively until an object of type
391 \fI<type>\fR
392 is found or the object cannot be dereferenced anymore (in which case, barf)\&. For example, if
393 \fI<rev>\fR
394 is a commit\-ish,
395 \fI<rev>^{commit}\fR
396 describes the corresponding commit object\&. Similarly, if
397 \fI<rev>\fR
398 is a tree\-ish,
399 \fI<rev>^{tree}\fR
400 describes the corresponding tree object\&.
401 \fI<rev>^0\fR
402 is a short\-hand for
403 \fI<rev>^{commit}\fR\&.
404 .sp
405 \fI<rev>^{object}\fR
406 can be used to make sure
407 \fI<rev>\fR
408 names an object that exists, without requiring
409 \fI<rev>\fR
410 to be a tag, and without dereferencing
411 \fI<rev>\fR; because a tag is already an object, it does not have to be dereferenced even once to get to an object\&.
412 .sp
413 \fI<rev>^{tag}\fR
414 can be used to ensure that
415 \fI<rev>\fR
416 identifies an existing tag object\&.
417 .RE
418 .PP
419 \fI<rev>^{}\fR, e\&.g\&. \fIv0\&.99\&.8^{}\fR
420 .RS 4
421 A suffix
422 \fI^\fR
423 followed by an empty brace pair means the object could be a tag, and dereference the tag recursively until a non\-tag object is found\&.
424 .RE
425 .PP
426 \fI<rev>^{/<text>}\fR, e\&.g\&. \fIHEAD^{/fix nasty bug}\fR
427 .RS 4
428 A suffix
429 \fI^\fR
430 to a revision parameter, followed by a brace pair that contains a text led by a slash, is the same as the
431 \fI:/fix nasty bug\fR
432 syntax below except that it returns the youngest matching commit which is reachable from the
433 \fI<rev>\fR
434 before
435 \fI^\fR\&.
436 .RE
437 .PP
438 \fI:/<text>\fR, e\&.g\&. \fI:/fix nasty bug\fR
439 .RS 4
440 A colon, followed by a slash, followed by a text, names a commit whose commit message matches the specified regular expression\&. This name returns the youngest matching commit which is reachable from any ref, including HEAD\&. The regular expression can match any part of the commit message\&. To match messages starting with a string, one can use e\&.g\&.
441 \fI:/^foo\fR\&. The special sequence
442 \fI:/!\fR
443 is reserved for modifiers to what is matched\&.
444 \fI:/!\-foo\fR
445 performs a negative match, while
446 \fI:/!!foo\fR
447 matches a literal
448 \fI!\fR
449 character, followed by
450 \fIfoo\fR\&. Any other sequence beginning with
451 \fI:/!\fR
452 is reserved for now\&. Depending on the given text, the shell\(cqs word splitting rules might require additional quoting\&.
453 .RE
454 .PP
455 \fI<rev>:<path>\fR, e\&.g\&. \fIHEAD:README\fR, \fImaster:\&./README\fR
456 .RS 4
457 A suffix
458 \fI:\fR
459 followed by a path names the blob or tree at the given path in the tree\-ish object named by the part before the colon\&. A path starting with
460 \fI\&./\fR
461 or
462 \fI\&.\&./\fR
463 is relative to the current working directory\&. The given path will be converted to be relative to the working tree\(cqs root directory\&. This is most useful to address a blob or tree from a commit or tree that has the same tree structure as the working tree\&.
464 .RE
465 .PP
466 \fI:[<n>:]<path>\fR, e\&.g\&. \fI:0:README\fR, \fI:README\fR
467 .RS 4
468 A colon, optionally followed by a stage number (0 to 3) and a colon, followed by a path, names a blob object in the index at the given path\&. A missing stage number (and the colon that follows it) names a stage 0 entry\&. During a merge, stage 1 is the common ancestor, stage 2 is the target branch\(cqs version (typically the current branch), and stage 3 is the version from the branch which is being merged\&.
469 .RE
470 .sp
471 Here is an illustration, by Jon Loeliger\&. Both commit nodes B and C are parents of commit node A\&. Parent commits are ordered left\-to\-right\&.
472 .sp
473 .if n \{\
474 .RS 4
475 .\}
476 .nf
477 G H I J
478 \e / \e /
479 D E F
480 \e | / \e
481 \e | / |
482 \e|/ |
483 B C
484 \e /
485 \e /
486 A
487 .fi
488 .if n \{\
489 .RE
490 .\}
491 .sp
492 .if n \{\
493 .RS 4
494 .\}
495 .nf
496 A = = A^0
497 B = A^ = A^1 = A~1
498 C = = A^2
499 D = A^^ = A^1^1 = A~2
500 E = B^2 = A^^2
501 F = B^3 = A^^3
502 G = A^^^ = A^1^1^1 = A~3
503 H = D^2 = B^^2 = A^^^2 = A~2^2
504 I = F^ = B^3^ = A^^3^
505 J = F^2 = B^3^2 = A^^3^2
506 .fi
507 .if n \{\
508 .RE
509 .\}
510 .SH "SPECIFYING RANGES"
511 .sp
512 History traversing commands such as \fBgit log\fR operate on a set of commits, not just a single commit\&.
513 .sp
514 For these commands, specifying a single revision, using the notation described in the previous section, means the set of commits \fBreachable\fR from the given commit\&.
515 .sp
516 Specifying several revisions means the set of commits reachable from any of the given commits\&.
517 .sp
518 A commit\(cqs reachable set is the commit itself and the commits in its ancestry chain\&.
519 .sp
520 There are several notations to specify a set of connected commits (called a "revision range"), illustrated below\&.
521 .SS "Commit Exclusions"
522 .PP
523 \fI^<rev>\fR (caret) Notation
524 .RS 4
525 To exclude commits reachable from a commit, a prefix
526 \fI^\fR
527 notation is used\&. E\&.g\&.
528 \fI^r1 r2\fR
529 means commits reachable from
530 \fIr2\fR
531 but exclude the ones reachable from
532 \fIr1\fR
533 (i\&.e\&.
534 \fIr1\fR
535 and its ancestors)\&.
536 .RE
537 .SS "Dotted Range Notations"
538 .PP
539 The \fI\&.\&.\fR (two\-dot) Range Notation
540 .RS 4
541 The
542 \fI^r1 r2\fR
543 set operation appears so often that there is a shorthand for it\&. When you have two commits
544 \fIr1\fR
545 and
546 \fIr2\fR
547 (named according to the syntax explained in SPECIFYING REVISIONS above), you can ask for commits that are reachable from r2 excluding those that are reachable from r1 by
548 \fI^r1 r2\fR
549 and it can be written as
550 \fIr1\&.\&.r2\fR\&.
551 .RE
552 .PP
553 The \fI\&.\&.\&.\fR (three\-dot) Symmetric Difference Notation
554 .RS 4
555 A similar notation
556 \fIr1\&.\&.\&.r2\fR
557 is called symmetric difference of
558 \fIr1\fR
559 and
560 \fIr2\fR
561 and is defined as
562 \fIr1 r2 \-\-not $(git merge\-base \-\-all r1 r2)\fR\&. It is the set of commits that are reachable from either one of
563 \fIr1\fR
564 (left side) or
565 \fIr2\fR
566 (right side) but not from both\&.
567 .RE
568 .sp
569 In these two shorthand notations, you can omit one end and let it default to HEAD\&. For example, \fIorigin\&.\&.\fR is a shorthand for \fIorigin\&.\&.HEAD\fR and asks "What did I do since I forked from the origin branch?" Similarly, \fI\&.\&.origin\fR is a shorthand for \fIHEAD\&.\&.origin\fR and asks "What did the origin do since I forked from them?" Note that \fI\&.\&.\fR would mean \fIHEAD\&.\&.HEAD\fR which is an empty range that is both reachable and unreachable from HEAD\&.
570 .sp
571 Commands that are specifically designed to take two distinct ranges (e\&.g\&. "git range\-diff R1 R2" to compare two ranges) do exist, but they are exceptions\&. Unless otherwise noted, all "git" commands that operate on a set of commits work on a single revision range\&. In other words, writing two "two\-dot range notation" next to each other, e\&.g\&.
572 .sp
573 .if n \{\
574 .RS 4
575 .\}
576 .nf
577 $ git log A\&.\&.B C\&.\&.D
578 .fi
579 .if n \{\
580 .RE
581 .\}
582 .sp
583 does \fBnot\fR specify two revision ranges for most commands\&. Instead it will name a single connected set of commits, i\&.e\&. those that are reachable from either B or D but are reachable from neither A or C\&. In a linear history like this:
584 .sp
585 .if n \{\
586 .RS 4
587 .\}
588 .nf
589 \-\-\-A\-\-\-B\-\-\-o\-\-\-o\-\-\-C\-\-\-D
590 .fi
591 .if n \{\
592 .RE
593 .\}
594 .sp
595 because A and B are reachable from C, the revision range specified by these two dotted ranges is a single commit D\&.
596 .SS "Other <rev>^ Parent Shorthand Notations"
597 .sp
598 Three other shorthands exist, particularly useful for merge commits, for naming a set that is formed by a commit and its parent commits\&.
599 .sp
600 The \fIr1^@\fR notation means all parents of \fIr1\fR\&.
601 .sp
602 The \fIr1^!\fR notation includes commit \fIr1\fR but excludes all of its parents\&. By itself, this notation denotes the single commit \fIr1\fR\&.
603 .sp
604 The \fI<rev>^\-[<n>]\fR notation includes \fI<rev>\fR but excludes the <n>th parent (i\&.e\&. a shorthand for \fI<rev>^<n>\&.\&.<rev>\fR), with \fI<n>\fR = 1 if not given\&. This is typically useful for merge commits where you can just pass \fI<commit>^\-\fR to get all the commits in the branch that was merged in merge commit \fI<commit>\fR (including \fI<commit>\fR itself)\&.
605 .sp
606 While \fI<rev>^<n>\fR was about specifying a single commit parent, these three notations also consider its parents\&. For example you can say \fIHEAD^2^@\fR, however you cannot say \fIHEAD^@^2\fR\&.
607 .SH "REVISION RANGE SUMMARY"
608 .PP
609 \fI<rev>\fR
610 .RS 4
611 Include commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
612 .RE
613 .PP
614 \fI^<rev>\fR
615 .RS 4
616 Exclude commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
617 .RE
618 .PP
619 \fI<rev1>\&.\&.<rev2>\fR
620 .RS 4
621 Include commits that are reachable from <rev2> but exclude those that are reachable from <rev1>\&. When either <rev1> or <rev2> is omitted, it defaults to
622 \fBHEAD\fR\&.
623 .RE
624 .PP
625 \fI<rev1>\&.\&.\&.<rev2>\fR
626 .RS 4
627 Include commits that are reachable from either <rev1> or <rev2> but exclude those that are reachable from both\&. When either <rev1> or <rev2> is omitted, it defaults to
628 \fBHEAD\fR\&.
629 .RE
630 .PP
631 \fI<rev>^@\fR, e\&.g\&. \fIHEAD^@\fR
632 .RS 4
633 A suffix
634 \fI^\fR
635 followed by an at sign is the same as listing all parents of
636 \fI<rev>\fR
637 (meaning, include anything reachable from its parents, but not the commit itself)\&.
638 .RE
639 .PP
640 \fI<rev>^!\fR, e\&.g\&. \fIHEAD^!\fR
641 .RS 4
642 A suffix
643 \fI^\fR
644 followed by an exclamation mark is the same as giving commit
645 \fI<rev>\fR
646 and all its parents prefixed with
647 \fI^\fR
648 to exclude them (and their ancestors)\&.
649 .RE
650 .PP
651 \fI<rev>^\-<n>\fR, e\&.g\&. \fIHEAD^\-, HEAD^\-2\fR
652 .RS 4
653 Equivalent to
654 \fI<rev>^<n>\&.\&.<rev>\fR, with
655 \fI<n>\fR
656 = 1 if not given\&.
657 .RE
658 .sp
659 Here are a handful of examples using the Loeliger illustration above, with each step in the notation\(cqs expansion and selection carefully spelt out:
660 .sp
661 .if n \{\
662 .RS 4
663 .\}
664 .nf
665 Args Expanded arguments Selected commits
666 D G H D
667 D F G H I J D F
668 ^G D H D
669 ^D B E I J F B
670 ^D B C E I J F B C
671 C I J F C
672 B\&.\&.C = ^B C C
673 B\&.\&.\&.C = B ^F C G H D E B C
674 B^\- = B^\&.\&.B
675 = ^B^1 B E I J F B
676 C^@ = C^1
677 = F I J F
678 B^@ = B^1 B^2 B^3
679 = D E F D G H E F I J
680 C^! = C ^C^@
681 = C ^C^1
682 = C ^F C
683 B^! = B ^B^@
684 = B ^B^1 ^B^2 ^B^3
685 = B ^D ^E ^F B
686 F^! D = F ^I ^J D G H D F
687 .fi
688 .if n \{\
689 .RE
690 .\}
691 .SH "SEE ALSO"
692 .sp
693 \fBgit-rev-parse\fR(1)
694 .SH "GIT"
695 .sp
696 Part of the \fBgit\fR(1) suite