| blob | ebd483f59208378e5b4e41246925bbd8865cb37c |
1 '\" t
2 .\" Title: gitrevisions
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
5 .\" Date: 2023-06-01
6 .\" Manual: Git Manual
7 .\" Source: Git 2.41.0
8 .\" Language: English
9 .\"
10 .TH "GITREVISIONS" "7" "2023\-06\-01" "Git 2\&.41\&.0" "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 and
102 \fBCHERRY_PICK_HEAD\fR);
103 .RE
104 .sp
105 .RS 4
106 .ie n \{\
107 \h'-04' 2.\h'+01'\c
108 .\}
109 .el \{\
110 .sp -1
111 .IP " 2." 4.2
112 .\}
113 otherwise,
114 \fIrefs/<refname>\fR
115 if it exists;
116 .RE
117 .sp
118 .RS 4
119 .ie n \{\
120 \h'-04' 3.\h'+01'\c
121 .\}
122 .el \{\
123 .sp -1
124 .IP " 3." 4.2
125 .\}
126 otherwise,
127 \fIrefs/tags/<refname>\fR
128 if it exists;
129 .RE
130 .sp
131 .RS 4
132 .ie n \{\
133 \h'-04' 4.\h'+01'\c
134 .\}
135 .el \{\
136 .sp -1
137 .IP " 4." 4.2
138 .\}
139 otherwise,
140 \fIrefs/heads/<refname>\fR
141 if it exists;
142 .RE
143 .sp
144 .RS 4
145 .ie n \{\
146 \h'-04' 5.\h'+01'\c
147 .\}
148 .el \{\
149 .sp -1
150 .IP " 5." 4.2
151 .\}
152 otherwise,
153 \fIrefs/remotes/<refname>\fR
154 if it exists;
155 .RE
156 .sp
157 .RS 4
158 .ie n \{\
159 \h'-04' 6.\h'+01'\c
160 .\}
161 .el \{\
162 .sp -1
163 .IP " 6." 4.2
164 .\}
165 otherwise,
166 \fIrefs/remotes/<refname>/HEAD\fR
167 if it exists\&.
168 .sp
169 \fBHEAD\fR
170 names the commit on which you based the changes in the working tree\&.
171 \fBFETCH_HEAD\fR
172 records the branch which you fetched from a remote repository with your last
173 \fBgit fetch\fR
174 invocation\&.
175 \fBORIG_HEAD\fR
176 is created by commands that move your
177 \fBHEAD\fR
178 in a drastic way (\fBgit am\fR,
179 \fBgit merge\fR,
180 \fBgit rebase\fR,
181 \fBgit reset\fR), to record the position of the
182 \fBHEAD\fR
183 before their operation, so that you can easily change the tip of the branch back to the state before you ran them\&.
184 \fBMERGE_HEAD\fR
185 records the commit(s) which you are merging into your branch when you run
186 \fBgit merge\fR\&.
187 \fBCHERRY_PICK_HEAD\fR
188 records the commit which you are cherry\-picking when you run
189 \fBgit cherry\-pick\fR\&.
190 .sp
191 Note that any of the
192 \fIrefs/*\fR
193 cases above may come either from the
194 \fB$GIT_DIR/refs\fR
195 directory or from the
196 \fB$GIT_DIR/packed\-refs\fR
197 file\&. While the ref name encoding is unspecified, UTF\-8 is preferred as some output processing may assume ref names in UTF\-8\&.
198 .RE
199 .RE
200 .PP
201 \fI@\fR
202 .RS 4
203 \fI@\fR
204 alone is a shortcut for
205 \fBHEAD\fR\&.
206 .RE
207 .PP
208 \fI[<refname>]@{<date>}\fR, e\&.g\&. \fImaster@{yesterday}\fR, \fIHEAD@{5 minutes ago}\fR
209 .RS 4
210 A ref followed by the suffix
211 \fI@\fR
212 with a date specification enclosed in a brace pair (e\&.g\&.
213 \fI{yesterday}\fR,
214 \fI{1 month 2 weeks 3 days 1 hour 1 second ago}\fR
215 or
216 \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
217 \fBlocal\fR
218 ref at a given time; e\&.g\&., what was in your local
219 \fImaster\fR
220 branch last week\&. If you want to look at commits made during certain times, see
221 \fB\-\-since\fR
222 and
223 \fB\-\-until\fR\&.
224 .RE
225 .PP
226 \fI<refname>@{<n>}\fR, e\&.g\&. \fImaster@{1}\fR
227 .RS 4
228 A ref followed by the suffix
229 \fI@\fR
230 with an ordinal specification enclosed in a brace pair (e\&.g\&.
231 \fI{1}\fR,
232 \fI{15}\fR) specifies the n\-th prior value of that ref\&. For example
233 \fImaster@{1}\fR
234 is the immediate prior value of
235 \fImaster\fR
236 while
237 \fImaster@{5}\fR
238 is the 5th prior value of
239 \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)\&.
240 .RE
241 .PP
242 \fI@{<n>}\fR, e\&.g\&. \fI@{1}\fR
243 .RS 4
244 You can use the
245 \fI@\fR
246 construct with an empty ref part to get at a reflog entry of the current branch\&. For example, if you are on branch
247 \fIblabla\fR
248 then
249 \fI@{1}\fR
250 means the same as
251 \fIblabla@{1}\fR\&.
252 .RE
253 .PP
254 \fI@{\-<n>}\fR, e\&.g\&. \fI@{\-1}\fR
255 .RS 4
256 The construct
257 \fI@{\-<n>}\fR
258 means the <n>th branch/commit checked out before the current one\&.
259 .RE
260 .PP
261 \fI[<branchname>]@{upstream}\fR, e\&.g\&. \fImaster@{upstream}\fR, \fI@{u}\fR
262 .RS 4
263 A branch B may be set up to build on top of a branch X (configured with
264 \fBbranch\&.<name>\&.merge\fR) at a remote R (configured with the branch X taken from remote R, typically found at
265 \fBrefs/remotes/R/X\fR\&.
266 .RE
267 .PP
268 \fI[<branchname>]@{push}\fR, e\&.g\&. \fImaster@{push}\fR, \fI@{push}\fR
269 .RS 4
270 The suffix
271 \fI@{push}\fR
272 reports the branch "where we would push to" if
273 \fBgit push\fR
274 were run while
275 \fBbranchname\fR
276 was checked out (or the current
277 \fBHEAD\fR
278 if no branchname is specified)\&. Like for
279 \fI@{upstream}\fR, we report the remote\-tracking branch that corresponds to that branch at the remote\&.
280 .sp
281 Here\(cqs an example to make it more clear:
282 .sp
283 .if n \{\
284 .RS 4
285 .\}
286 .nf
287 $ git config push\&.default current
288 $ git config remote\&.pushdefault myfork
289 $ git switch \-c mybranch origin/master
291 $ git rev\-parse \-\-symbolic\-full\-name @{upstream}
292 refs/remotes/origin/master
294 $ git rev\-parse \-\-symbolic\-full\-name @{push}
295 refs/remotes/myfork/mybranch
296 .fi
297 .if n \{\
298 .RE
299 .\}
300 .sp
301 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,
302 \fI@{push}\fR
303 is the same as
304 \fI@{upstream}\fR, and there is no need for it\&.
305 .sp
306 This suffix is also accepted when spelled in uppercase, and means the same thing no matter the case\&.
307 .RE
308 .PP
309 \fI<rev>^[<n>]\fR, e\&.g\&. \fIHEAD^, v1\&.5\&.1^0\fR
310 .RS 4
311 A suffix
312 \fI^\fR
313 to a revision parameter means the first parent of that commit object\&.
314 \fI^<n>\fR
315 means the <n>th parent (i\&.e\&.
316 \fI<rev>^\fR
317 is equivalent to
318 \fI<rev>^1\fR)\&. As a special rule,
319 \fI<rev>^0\fR
320 means the commit itself and is used when
321 \fI<rev>\fR
322 is the object name of a tag object that refers to a commit object\&.
323 .RE
324 .PP
325 \fI<rev>~[<n>]\fR, e\&.g\&. \fIHEAD~, master~3\fR
326 .RS 4
327 A suffix
328 \fI~\fR
329 to a revision parameter means the first parent of that commit object\&. A suffix
330 \fI~<n>\fR
331 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\&.
332 \fI<rev>~3\fR
333 is equivalent to
334 \fI<rev>^^^\fR
335 which is equivalent to
336 \fI<rev>^1^1^1\fR\&. See below for an illustration of the usage of this form\&.
337 .RE
338 .PP
339 \fI<rev>^{<type>}\fR, e\&.g\&. \fIv0\&.99\&.8^{commit}\fR
340 .RS 4
341 A suffix
342 \fI^\fR
343 followed by an object type name enclosed in brace pair means dereference the object at
344 \fI<rev>\fR
345 recursively until an object of type
346 \fI<type>\fR
347 is found or the object cannot be dereferenced anymore (in which case, barf)\&. For example, if
348 \fI<rev>\fR
349 is a commit\-ish,
350 \fI<rev>^{commit}\fR
351 describes the corresponding commit object\&. Similarly, if
352 \fI<rev>\fR
353 is a tree\-ish,
354 \fI<rev>^{tree}\fR
355 describes the corresponding tree object\&.
356 \fI<rev>^0\fR
357 is a short\-hand for
358 \fI<rev>^{commit}\fR\&.
359 .sp
360 \fI<rev>^{object}\fR
361 can be used to make sure
362 \fI<rev>\fR
363 names an object that exists, without requiring
364 \fI<rev>\fR
365 to be a tag, and without dereferencing
366 \fI<rev>\fR; because a tag is already an object, it does not have to be dereferenced even once to get to an object\&.
367 .sp
368 \fI<rev>^{tag}\fR
369 can be used to ensure that
370 \fI<rev>\fR
371 identifies an existing tag object\&.
372 .RE
373 .PP
374 \fI<rev>^{}\fR, e\&.g\&. \fIv0\&.99\&.8^{}\fR
375 .RS 4
376 A suffix
377 \fI^\fR
378 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\&.
379 .RE
380 .PP
381 \fI<rev>^{/<text>}\fR, e\&.g\&. \fIHEAD^{/fix nasty bug}\fR
382 .RS 4
383 A suffix
384 \fI^\fR
385 to a revision parameter, followed by a brace pair that contains a text led by a slash, is the same as the
386 \fI:/fix nasty bug\fR
387 syntax below except that it returns the youngest matching commit which is reachable from the
388 \fI<rev>\fR
389 before
390 \fI^\fR\&.
391 .RE
392 .PP
393 \fI:/<text>\fR, e\&.g\&. \fI:/fix nasty bug\fR
394 .RS 4
395 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\&.
396 \fI:/^foo\fR\&. The special sequence
397 \fI:/!\fR
398 is reserved for modifiers to what is matched\&.
399 \fI:/!\-foo\fR
400 performs a negative match, while
401 \fI:/!!foo\fR
402 matches a literal
403 \fI!\fR
404 character, followed by
405 \fIfoo\fR\&. Any other sequence beginning with
406 \fI:/!\fR
407 is reserved for now\&. Depending on the given text, the shell\(cqs word splitting rules might require additional quoting\&.
408 .RE
409 .PP
410 \fI<rev>:<path>\fR, e\&.g\&. \fIHEAD:README\fR, \fImaster:\&./README\fR
411 .RS 4
412 A suffix
413 \fI:\fR
414 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
415 \fI\&./\fR
416 or
417 \fI\&.\&./\fR
418 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\&.
419 .RE
420 .PP
421 \fI:[<n>:]<path>\fR, e\&.g\&. \fI:0:README\fR, \fI:README\fR
422 .RS 4
423 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\&.
424 .RE
425 .sp
426 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\&.
427 .sp
428 .if n \{\
429 .RS 4
430 .\}
431 .nf
432 G H I J
433 \e / \e /
434 D E F
435 \e | / \e
436 \e | / |
437 \e|/ |
438 B C
439 \e /
440 \e /
441 A
442 .fi
443 .if n \{\
444 .RE
445 .\}
446 .sp
447 .if n \{\
448 .RS 4
449 .\}
450 .nf
451 A = = A^0
452 B = A^ = A^1 = A~1
453 C = = A^2
454 D = A^^ = A^1^1 = A~2
455 E = B^2 = A^^2
456 F = B^3 = A^^3
457 G = A^^^ = A^1^1^1 = A~3
458 H = D^2 = B^^2 = A^^^2 = A~2^2
459 I = F^ = B^3^ = A^^3^
460 J = F^2 = B^3^2 = A^^3^2
461 .fi
462 .if n \{\
463 .RE
464 .\}
465 .SH "SPECIFYING RANGES"
466 .sp
467 History traversing commands such as \fBgit log\fR operate on a set of commits, not just a single commit\&.
468 .sp
469 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\&.
470 .sp
471 Specifying several revisions means the set of commits reachable from any of the given commits\&.
472 .sp
473 A commit\(cqs reachable set is the commit itself and the commits in its ancestry chain\&.
474 .sp
475 There are several notations to specify a set of connected commits (called a "revision range"), illustrated below\&.
476 .SS "Commit Exclusions"
477 .PP
478 \fI^<rev>\fR (caret) Notation
479 .RS 4
480 To exclude commits reachable from a commit, a prefix
481 \fI^\fR
482 notation is used\&. E\&.g\&.
483 \fI^r1 r2\fR
484 means commits reachable from
485 \fIr2\fR
486 but exclude the ones reachable from
487 \fIr1\fR
488 (i\&.e\&.
489 \fIr1\fR
490 and its ancestors)\&.
491 .RE
492 .SS "Dotted Range Notations"
493 .PP
494 The \fI\&.\&.\fR (two\-dot) Range Notation
495 .RS 4
496 The
497 \fI^r1 r2\fR
498 set operation appears so often that there is a shorthand for it\&. When you have two commits
499 \fIr1\fR
500 and
501 \fIr2\fR
502 (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
503 \fI^r1 r2\fR
504 and it can be written as
505 \fIr1\&.\&.r2\fR\&.
506 .RE
507 .PP
508 The \fI\&.\&.\&.\fR (three\-dot) Symmetric Difference Notation
509 .RS 4
510 A similar notation
511 \fIr1\&.\&.\&.r2\fR
512 is called symmetric difference of
513 \fIr1\fR
514 and
515 \fIr2\fR
516 and is defined as
517 \fIr1 r2 \-\-not $(git merge\-base \-\-all r1 r2)\fR\&. It is the set of commits that are reachable from either one of
518 \fIr1\fR
519 (left side) or
520 \fIr2\fR
521 (right side) but not from both\&.
522 .RE
523 .sp
524 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\&.
525 .sp
526 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\&.
527 .sp
528 .if n \{\
529 .RS 4
530 .\}
531 .nf
532 $ git log A\&.\&.B C\&.\&.D
533 .fi
534 .if n \{\
535 .RE
536 .\}
537 .sp
538 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:
539 .sp
540 .if n \{\
541 .RS 4
542 .\}
543 .nf
544 \-\-\-A\-\-\-B\-\-\-o\-\-\-o\-\-\-C\-\-\-D
545 .fi
546 .if n \{\
547 .RE
548 .\}
549 .sp
550 because A and B are reachable from C, the revision range specified by these two dotted ranges is a single commit D\&.
551 .SS "Other <rev>^ Parent Shorthand Notations"
552 .sp
553 Three other shorthands exist, particularly useful for merge commits, for naming a set that is formed by a commit and its parent commits\&.
554 .sp
555 The \fIr1^@\fR notation means all parents of \fIr1\fR\&.
556 .sp
557 The \fIr1^!\fR notation includes commit \fIr1\fR but excludes all of its parents\&. By itself, this notation denotes the single commit \fIr1\fR\&.
558 .sp
559 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)\&.
560 .sp
561 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\&.
562 .SH "REVISION RANGE SUMMARY"
563 .PP
564 \fI<rev>\fR
565 .RS 4
566 Include commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
567 .RE
568 .PP
569 \fI^<rev>\fR
570 .RS 4
571 Exclude commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
572 .RE
573 .PP
574 \fI<rev1>\&.\&.<rev2>\fR
575 .RS 4
576 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
577 \fBHEAD\fR\&.
578 .RE
579 .PP
580 \fI<rev1>\&.\&.\&.<rev2>\fR
581 .RS 4
582 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
583 \fBHEAD\fR\&.
584 .RE
585 .PP
586 \fI<rev>^@\fR, e\&.g\&. \fIHEAD^@\fR
587 .RS 4
588 A suffix
589 \fI^\fR
590 followed by an at sign is the same as listing all parents of
591 \fI<rev>\fR
592 (meaning, include anything reachable from its parents, but not the commit itself)\&.
593 .RE
594 .PP
595 \fI<rev>^!\fR, e\&.g\&. \fIHEAD^!\fR
596 .RS 4
597 A suffix
598 \fI^\fR
599 followed by an exclamation mark is the same as giving commit
600 \fI<rev>\fR
601 and all its parents prefixed with
602 \fI^\fR
603 to exclude them (and their ancestors)\&.
604 .RE
605 .PP
606 \fI<rev>^\-<n>\fR, e\&.g\&. \fIHEAD^\-, HEAD^\-2\fR
607 .RS 4
608 Equivalent to
609 \fI<rev>^<n>\&.\&.<rev>\fR, with
610 \fI<n>\fR
611 = 1 if not given\&.
612 .RE
613 .sp
614 Here are a handful of examples using the Loeliger illustration above, with each step in the notation\(cqs expansion and selection carefully spelt out:
615 .sp
616 .if n \{\
617 .RS 4
618 .\}
619 .nf
620 Args Expanded arguments Selected commits
621 D G H D
622 D F G H I J D F
623 ^G D H D
624 ^D B E I J F B
625 ^D B C E I J F B C
626 C I J F C
627 B\&.\&.C = ^B C C
628 B\&.\&.\&.C = B ^F C G H D E B C
629 B^\- = B^\&.\&.B
630 = ^B^1 B E I J F B
631 C^@ = C^1
632 = F I J F
633 B^@ = B^1 B^2 B^3
634 = D E F D G H E F I J
635 C^! = C ^C^@
636 = C ^C^1
637 = C ^F C
638 B^! = B ^B^@
639 = B ^B^1 ^B^2 ^B^3
640 = B ^D ^E ^F B
641 F^! D = F ^I ^J D G H D F
642 .fi
643 .if n \{\
644 .RE
645 .\}
646 .SH "SEE ALSO"
647 .sp
648 \fBgit-rev-parse\fR(1)
649 .SH "GIT"
650 .sp
651 Part of the \fBgit\fR(1) suite