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