| blob | bd22c6aa0a3d94bf428ef3f6fe9b7715c699ee6a |
1 '\" t
2 .\" Title: git-rev-parse
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: 01/03/2022
6 .\" Manual: Git Manual
7 .\" Source: Git 2.34.1.428.gdcc0cd074f
8 .\" Language: English
9 .\"
10 .TH "GIT\-REV\-PARSE" "1" "01/03/2022" "Git 2\&.34\&.1\&.428\&.gdcc0cd" "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 git-rev-parse \- Pick out and massage parameters
32 .SH "SYNOPSIS"
33 .sp
34 .nf
35 \fIgit rev\-parse\fR [<options>] <args>\&...
36 .fi
37 .sp
38 .SH "DESCRIPTION"
39 .sp
40 Many Git porcelainish commands take mixture of flags (i\&.e\&. parameters that begin with a dash \fI\-\fR) and parameters meant for the underlying \fIgit rev\-list\fR command they use internally and flags and parameters for the other commands they use downstream of \fIgit rev\-list\fR\&. This command is used to distinguish between them\&.
41 .SH "OPTIONS"
42 .SS "Operation Modes"
43 .sp
44 Each of these options must appear first on the command line\&.
45 .PP
46 \-\-parseopt
47 .RS 4
48 Use
49 \fIgit rev\-parse\fR
50 in option parsing mode (see PARSEOPT section below)\&.
51 .RE
52 .PP
53 \-\-sq\-quote
54 .RS 4
55 Use
56 \fIgit rev\-parse\fR
57 in shell quoting mode (see SQ\-QUOTE section below)\&. In contrast to the
58 \fB\-\-sq\fR
59 option below, this mode does only quoting\&. Nothing else is done to command input\&.
60 .RE
61 .SS "Options for \-\-parseopt"
62 .PP
63 \-\-keep\-dashdash
64 .RS 4
65 Only meaningful in
66 \fB\-\-parseopt\fR
67 mode\&. Tells the option parser to echo out the first
68 \fB\-\-\fR
69 met instead of skipping it\&.
70 .RE
71 .PP
72 \-\-stop\-at\-non\-option
73 .RS 4
74 Only meaningful in
75 \fB\-\-parseopt\fR
76 mode\&. Lets the option parser stop at the first non\-option argument\&. This can be used to parse sub\-commands that take options themselves\&.
77 .RE
78 .PP
79 \-\-stuck\-long
80 .RS 4
81 Only meaningful in
82 \fB\-\-parseopt\fR
83 mode\&. Output the options in their long form if available, and with their arguments stuck\&.
84 .RE
85 .SS "Options for Filtering"
86 .PP
87 \-\-revs\-only
88 .RS 4
89 Do not output flags and parameters not meant for
90 \fIgit rev\-list\fR
91 command\&.
92 .RE
93 .PP
94 \-\-no\-revs
95 .RS 4
96 Do not output flags and parameters meant for
97 \fIgit rev\-list\fR
98 command\&.
99 .RE
100 .PP
101 \-\-flags
102 .RS 4
103 Do not output non\-flag parameters\&.
104 .RE
105 .PP
106 \-\-no\-flags
107 .RS 4
108 Do not output flag parameters\&.
109 .RE
110 .SS "Options for Output"
111 .PP
112 \-\-default <arg>
113 .RS 4
114 If there is no parameter given by the user, use
115 \fB<arg>\fR
116 instead\&.
117 .RE
118 .PP
119 \-\-prefix <arg>
120 .RS 4
121 Behave as if
122 \fIgit rev\-parse\fR
123 was invoked from the
124 \fB<arg>\fR
125 subdirectory of the working tree\&. Any relative filenames are resolved as if they are prefixed by
126 \fB<arg>\fR
127 and will be printed in that form\&.
128 .sp
129 This can be used to convert arguments to a command run in a subdirectory so that they can still be used after moving to the top\-level of the repository\&. For example:
130 .sp
131 .if n \{\
132 .RS 4
133 .\}
134 .nf
135 prefix=$(git rev\-parse \-\-show\-prefix)
136 cd "$(git rev\-parse \-\-show\-toplevel)"
137 # rev\-parse provides the \-\- needed for \(aqset\(aq
138 eval "set $(git rev\-parse \-\-sq \-\-prefix "$prefix" \-\- "$@")"
139 .fi
140 .if n \{\
141 .RE
142 .\}
143 .sp
144 .RE
145 .PP
146 \-\-verify
147 .RS 4
148 Verify that exactly one parameter is provided, and that it can be turned into a raw 20\-byte SHA\-1 that can be used to access the object database\&. If so, emit it to the standard output; otherwise, error out\&.
149 .sp
150 If you want to make sure that the output actually names an object in your object database and/or can be used as a specific type of object you require, you can add the
151 \fB^{type}\fR
152 peeling operator to the parameter\&. For example,
153 \fBgit rev\-parse "$VAR^{commit}"\fR
154 will make sure
155 \fB$VAR\fR
156 names an existing object that is a commit\-ish (i\&.e\&. a commit, or an annotated tag that points at a commit)\&. To make sure that
157 \fB$VAR\fR
158 names an existing object of any type,
159 \fBgit rev\-parse "$VAR^{object}"\fR
160 can be used\&.
161 .sp
162 Note that if you are verifying a name from an untrusted source, it is wise to use
163 \fB\-\-end\-of\-options\fR
164 so that the name argument is not mistaken for another option\&.
165 .RE
166 .PP
167 \-q, \-\-quiet
168 .RS 4
169 Only meaningful in
170 \fB\-\-verify\fR
171 mode\&. Do not output an error message if the first argument is not a valid object name; instead exit with non\-zero status silently\&. SHA\-1s for valid object names are printed to stdout on success\&.
172 .RE
173 .PP
174 \-\-sq
175 .RS 4
176 Usually the output is made one line per flag and parameter\&. This option makes output a single line, properly quoted for consumption by shell\&. Useful when you expect your parameter to contain whitespaces and newlines (e\&.g\&. when using pickaxe
177 \fB\-S\fR
178 with
179 \fIgit diff\-*\fR)\&. In contrast to the
180 \fB\-\-sq\-quote\fR
181 option, the command input is still interpreted as usual\&.
182 .RE
183 .PP
184 \-\-short[=length]
185 .RS 4
186 Same as
187 \fB\-\-verify\fR
188 but shortens the object name to a unique prefix with at least
189 \fBlength\fR
190 characters\&. The minimum length is 4, the default is the effective value of the
191 \fBcore\&.abbrev\fR
192 configuration variable (see
193 \fBgit-config\fR(1))\&.
194 .RE
195 .PP
196 \-\-not
197 .RS 4
198 When showing object names, prefix them with
199 \fI^\fR
200 and strip
201 \fI^\fR
202 prefix from the object names that already have one\&.
203 .RE
204 .PP
205 \-\-abbrev\-ref[=(strict|loose)]
206 .RS 4
207 A non\-ambiguous short name of the objects name\&. The option core\&.warnAmbiguousRefs is used to select the strict abbreviation mode\&.
208 .RE
209 .PP
210 \-\-symbolic
211 .RS 4
212 Usually the object names are output in SHA\-1 form (with possible
213 \fI^\fR
214 prefix); this option makes them output in a form as close to the original input as possible\&.
215 .RE
216 .PP
217 \-\-symbolic\-full\-name
218 .RS 4
219 This is similar to \-\-symbolic, but it omits input that are not refs (i\&.e\&. branch or tag names; or more explicitly disambiguating "heads/master" form, when you want to name the "master" branch when there is an unfortunately named tag "master"), and show them as full refnames (e\&.g\&. "refs/heads/master")\&.
220 .RE
221 .SS "Options for Objects"
222 .PP
223 \-\-all
224 .RS 4
225 Show all refs found in
226 \fBrefs/\fR\&.
227 .RE
228 .PP
229 \-\-branches[=pattern], \-\-tags[=pattern], \-\-remotes[=pattern]
230 .RS 4
231 Show all branches, tags, or remote\-tracking branches, respectively (i\&.e\&., refs found in
232 \fBrefs/heads\fR,
233 \fBrefs/tags\fR, or
234 \fBrefs/remotes\fR, respectively)\&.
235 .sp
236 If a
237 \fBpattern\fR
238 is given, only refs matching the given shell glob are shown\&. If the pattern does not contain a globbing character (\fB?\fR,
239 \fB*\fR, or
240 \fB[\fR), it is turned into a prefix match by appending
241 \fB/*\fR\&.
242 .RE
243 .PP
244 \-\-glob=pattern
245 .RS 4
246 Show all refs matching the shell glob pattern
247 \fBpattern\fR\&. If the pattern does not start with
248 \fBrefs/\fR, this is automatically prepended\&. If the pattern does not contain a globbing character (\fB?\fR,
249 \fB*\fR, or
250 \fB[\fR), it is turned into a prefix match by appending
251 \fB/*\fR\&.
252 .RE
253 .PP
254 \-\-exclude=<glob\-pattern>
255 .RS 4
256 Do not include refs matching
257 \fI<glob\-pattern>\fR
258 that the next
259 \fB\-\-all\fR,
260 \fB\-\-branches\fR,
261 \fB\-\-tags\fR,
262 \fB\-\-remotes\fR, or
263 \fB\-\-glob\fR
264 would otherwise consider\&. Repetitions of this option accumulate exclusion patterns up to the next
265 \fB\-\-all\fR,
266 \fB\-\-branches\fR,
267 \fB\-\-tags\fR,
268 \fB\-\-remotes\fR, or
269 \fB\-\-glob\fR
270 option (other options or arguments do not clear accumulated patterns)\&.
271 .sp
272 The patterns given should not begin with
273 \fBrefs/heads\fR,
274 \fBrefs/tags\fR, or
275 \fBrefs/remotes\fR
276 when applied to
277 \fB\-\-branches\fR,
278 \fB\-\-tags\fR, or
279 \fB\-\-remotes\fR, respectively, and they must begin with
280 \fBrefs/\fR
281 when applied to
282 \fB\-\-glob\fR
283 or
284 \fB\-\-all\fR\&. If a trailing
285 \fI/*\fR
286 is intended, it must be given explicitly\&.
287 .RE
288 .PP
289 \-\-disambiguate=<prefix>
290 .RS 4
291 Show every object whose name begins with the given prefix\&. The <prefix> must be at least 4 hexadecimal digits long to avoid listing each and every object in the repository by mistake\&.
292 .RE
293 .SS "Options for Files"
294 .PP
295 \-\-local\-env\-vars
296 .RS 4
297 List the GIT_* environment variables that are local to the repository (e\&.g\&. GIT_DIR or GIT_WORK_TREE, but not GIT_EDITOR)\&. Only the names of the variables are listed, not their value, even if they are set\&.
298 .RE
299 .PP
300 \-\-path\-format=(absolute|relative)
301 .RS 4
302 Controls the behavior of certain other options\&. If specified as absolute, the paths printed by those options will be absolute and canonical\&. If specified as relative, the paths will be relative to the current working directory if that is possible\&. The default is option specific\&.
303 .sp
304 This option may be specified multiple times and affects only the arguments that follow it on the command line, either to the end of the command line or the next instance of this option\&.
305 .RE
306 .sp
307 The following options are modified by \fB\-\-path\-format\fR:
308 .PP
309 \-\-git\-dir
310 .RS 4
311 Show
312 \fB$GIT_DIR\fR
313 if defined\&. Otherwise show the path to the \&.git directory\&. The path shown, when relative, is relative to the current working directory\&.
314 .sp
315 If
316 \fB$GIT_DIR\fR
317 is not defined and the current directory is not detected to lie in a Git repository or work tree print a message to stderr and exit with nonzero status\&.
318 .RE
319 .PP
320 \-\-git\-common\-dir
321 .RS 4
322 Show
323 \fB$GIT_COMMON_DIR\fR
324 if defined, else
325 \fB$GIT_DIR\fR\&.
326 .RE
327 .PP
328 \-\-resolve\-git\-dir <path>
329 .RS 4
330 Check if <path> is a valid repository or a gitfile that points at a valid repository, and print the location of the repository\&. If <path> is a gitfile then the resolved path to the real repository is printed\&.
331 .RE
332 .PP
333 \-\-git\-path <path>
334 .RS 4
335 Resolve "$GIT_DIR/<path>" and takes other path relocation variables such as $GIT_OBJECT_DIRECTORY, $GIT_INDEX_FILE\&... into account\&. For example, if $GIT_OBJECT_DIRECTORY is set to /foo/bar then "git rev\-parse \-\-git\-path objects/abc" returns /foo/bar/abc\&.
336 .RE
337 .PP
338 \-\-show\-toplevel
339 .RS 4
340 Show the (by default, absolute) path of the top\-level directory of the working tree\&. If there is no working tree, report an error\&.
341 .RE
342 .PP
343 \-\-show\-superproject\-working\-tree
344 .RS 4
345 Show the absolute path of the root of the superproject\(cqs working tree (if exists) that uses the current repository as its submodule\&. Outputs nothing if the current repository is not used as a submodule by any project\&.
346 .RE
347 .PP
348 \-\-shared\-index\-path
349 .RS 4
350 Show the path to the shared index file in split index mode, or empty if not in split\-index mode\&.
351 .RE
352 .sp
353 The following options are unaffected by \fB\-\-path\-format\fR:
354 .PP
355 \-\-absolute\-git\-dir
356 .RS 4
357 Like
358 \fB\-\-git\-dir\fR, but its output is always the canonicalized absolute path\&.
359 .RE
360 .PP
361 \-\-is\-inside\-git\-dir
362 .RS 4
363 When the current working directory is below the repository directory print "true", otherwise "false"\&.
364 .RE
365 .PP
366 \-\-is\-inside\-work\-tree
367 .RS 4
368 When the current working directory is inside the work tree of the repository print "true", otherwise "false"\&.
369 .RE
370 .PP
371 \-\-is\-bare\-repository
372 .RS 4
373 When the repository is bare print "true", otherwise "false"\&.
374 .RE
375 .PP
376 \-\-is\-shallow\-repository
377 .RS 4
378 When the repository is shallow print "true", otherwise "false"\&.
379 .RE
380 .PP
381 \-\-show\-cdup
382 .RS 4
383 When the command is invoked from a subdirectory, show the path of the top\-level directory relative to the current directory (typically a sequence of "\&.\&./", or an empty string)\&.
384 .RE
385 .PP
386 \-\-show\-prefix
387 .RS 4
388 When the command is invoked from a subdirectory, show the path of the current directory relative to the top\-level directory\&.
389 .RE
390 .PP
391 \-\-show\-object\-format[=(storage|input|output)]
392 .RS 4
393 Show the object format (hash algorithm) used for the repository for storage inside the
394 \fB\&.git\fR
395 directory, input, or output\&. For input, multiple algorithms may be printed, space\-separated\&. If not specified, the default is "storage"\&.
396 .RE
397 .SS "Other Options"
398 .PP
399 \-\-since=datestring, \-\-after=datestring
400 .RS 4
401 Parse the date string, and output the corresponding \-\-max\-age= parameter for
402 \fIgit rev\-list\fR\&.
403 .RE
404 .PP
405 \-\-until=datestring, \-\-before=datestring
406 .RS 4
407 Parse the date string, and output the corresponding \-\-min\-age= parameter for
408 \fIgit rev\-list\fR\&.
409 .RE
410 .PP
411 <args>\&...
412 .RS 4
413 Flags and parameters to be parsed\&.
414 .RE
415 .SH "SPECIFYING REVISIONS"
416 .sp
417 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\&.
418 .if n \{\
419 .sp
420 .\}
421 .RS 4
422 .it 1 an-trap
423 .nr an-no-space-flag 1
424 .nr an-break-flag 1
425 .br
426 .ps +1
427 \fBNote\fR
428 .ps -1
429 .br
430 .sp
431 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\&.
432 .sp .5v
433 .RE
434 .PP
435 \fI<sha1>\fR, e\&.g\&. \fIdae86e1950b1277e545cee180551750029cfe735\fR, \fIdae86e\fR
436 .RS 4
437 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\&.
438 .RE
439 .PP
440 \fI<describeOutput>\fR, e\&.g\&. \fIv1\&.7\&.4\&.2\-679\-g3bee7fb\fR
441 .RS 4
442 Output from
443 \fBgit describe\fR; i\&.e\&. a closest tag, optionally followed by a dash and a number of commits, followed by a dash, a
444 \fIg\fR, and an abbreviated object name\&.
445 .RE
446 .PP
447 \fI<refname>\fR, e\&.g\&. \fImaster\fR, \fIheads/master\fR, \fIrefs/heads/master\fR
448 .RS 4
449 A symbolic ref name\&. E\&.g\&.
450 \fImaster\fR
451 typically means the commit object referenced by
452 \fIrefs/heads/master\fR\&. If you happen to have both
453 \fIheads/master\fR
454 and
455 \fItags/master\fR, you can explicitly say
456 \fIheads/master\fR
457 to tell Git which one you mean\&. When ambiguous, a
458 \fI<refname>\fR
459 is disambiguated by taking the first match in the following rules:
460 .sp
461 .RS 4
462 .ie n \{\
463 \h'-04' 1.\h'+01'\c
464 .\}
465 .el \{\
466 .sp -1
467 .IP " 1." 4.2
468 .\}
469 If
470 \fI$GIT_DIR/<refname>\fR
471 exists, that is what you mean (this is usually useful only for
472 \fBHEAD\fR,
473 \fBFETCH_HEAD\fR,
474 \fBORIG_HEAD\fR,
475 \fBMERGE_HEAD\fR
476 and
477 \fBCHERRY_PICK_HEAD\fR);
478 .RE
479 .sp
480 .RS 4
481 .ie n \{\
482 \h'-04' 2.\h'+01'\c
483 .\}
484 .el \{\
485 .sp -1
486 .IP " 2." 4.2
487 .\}
488 otherwise,
489 \fIrefs/<refname>\fR
490 if it exists;
491 .RE
492 .sp
493 .RS 4
494 .ie n \{\
495 \h'-04' 3.\h'+01'\c
496 .\}
497 .el \{\
498 .sp -1
499 .IP " 3." 4.2
500 .\}
501 otherwise,
502 \fIrefs/tags/<refname>\fR
503 if it exists;
504 .RE
505 .sp
506 .RS 4
507 .ie n \{\
508 \h'-04' 4.\h'+01'\c
509 .\}
510 .el \{\
511 .sp -1
512 .IP " 4." 4.2
513 .\}
514 otherwise,
515 \fIrefs/heads/<refname>\fR
516 if it exists;
517 .RE
518 .sp
519 .RS 4
520 .ie n \{\
521 \h'-04' 5.\h'+01'\c
522 .\}
523 .el \{\
524 .sp -1
525 .IP " 5." 4.2
526 .\}
527 otherwise,
528 \fIrefs/remotes/<refname>\fR
529 if it exists;
530 .RE
531 .sp
532 .RS 4
533 .ie n \{\
534 \h'-04' 6.\h'+01'\c
535 .\}
536 .el \{\
537 .sp -1
538 .IP " 6." 4.2
539 .\}
540 otherwise,
541 \fIrefs/remotes/<refname>/HEAD\fR
542 if it exists\&.
543 .sp
544 \fBHEAD\fR
545 names the commit on which you based the changes in the working tree\&.
546 \fBFETCH_HEAD\fR
547 records the branch which you fetched from a remote repository with your last
548 \fBgit fetch\fR
549 invocation\&.
550 \fBORIG_HEAD\fR
551 is created by commands that move your
552 \fBHEAD\fR
553 in a drastic way, to record the position of the
554 \fBHEAD\fR
555 before their operation, so that you can easily change the tip of the branch back to the state before you ran them\&.
556 \fBMERGE_HEAD\fR
557 records the commit(s) which you are merging into your branch when you run
558 \fBgit merge\fR\&.
559 \fBCHERRY_PICK_HEAD\fR
560 records the commit which you are cherry\-picking when you run
561 \fBgit cherry\-pick\fR\&.
562 .sp
563 Note that any of the
564 \fIrefs/*\fR
565 cases above may come either from the
566 \fB$GIT_DIR/refs\fR
567 directory or from the
568 \fB$GIT_DIR/packed\-refs\fR
569 file\&. While the ref name encoding is unspecified, UTF\-8 is preferred as some output processing may assume ref names in UTF\-8\&.
570 .RE
571 .RE
572 .PP
573 \fI@\fR
574 .RS 4
575 \fI@\fR
576 alone is a shortcut for
577 \fBHEAD\fR\&.
578 .RE
579 .PP
580 \fI[<refname>]@{<date>}\fR, e\&.g\&. \fImaster@{yesterday}\fR, \fIHEAD@{5 minutes ago}\fR
581 .RS 4
582 A ref followed by the suffix
583 \fI@\fR
584 with a date specification enclosed in a brace pair (e\&.g\&.
585 \fI{yesterday}\fR,
586 \fI{1 month 2 weeks 3 days 1 hour 1 second ago}\fR
587 or
588 \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
589 \fBlocal\fR
590 ref at a given time; e\&.g\&., what was in your local
591 \fImaster\fR
592 branch last week\&. If you want to look at commits made during certain times, see
593 \fB\-\-since\fR
594 and
595 \fB\-\-until\fR\&.
596 .RE
597 .PP
598 \fI<refname>@{<n>}\fR, e\&.g\&. \fImaster@{1}\fR
599 .RS 4
600 A ref followed by the suffix
601 \fI@\fR
602 with an ordinal specification enclosed in a brace pair (e\&.g\&.
603 \fI{1}\fR,
604 \fI{15}\fR) specifies the n\-th prior value of that ref\&. For example
605 \fImaster@{1}\fR
606 is the immediate prior value of
607 \fImaster\fR
608 while
609 \fImaster@{5}\fR
610 is the 5th prior value of
611 \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)\&.
612 .RE
613 .PP
614 \fI@{<n>}\fR, e\&.g\&. \fI@{1}\fR
615 .RS 4
616 You can use the
617 \fI@\fR
618 construct with an empty ref part to get at a reflog entry of the current branch\&. For example, if you are on branch
619 \fIblabla\fR
620 then
621 \fI@{1}\fR
622 means the same as
623 \fIblabla@{1}\fR\&.
624 .RE
625 .PP
626 \fI@{\-<n>}\fR, e\&.g\&. \fI@{\-1}\fR
627 .RS 4
628 The construct
629 \fI@{\-<n>}\fR
630 means the <n>th branch/commit checked out before the current one\&.
631 .RE
632 .PP
633 \fI[<branchname>]@{upstream}\fR, e\&.g\&. \fImaster@{upstream}\fR, \fI@{u}\fR
634 .RS 4
635 The suffix
636 \fI@{upstream}\fR
637 to a branchname (short form
638 \fI<branchname>@{u}\fR) refers to the branch that the branch specified by branchname is set to build on top of (configured with
639 \fBbranch\&.<name>\&.remote\fR
640 and
641 \fBbranch\&.<name>\&.merge\fR)\&. A missing branchname defaults to the current one\&. These suffixes are also accepted when spelled in uppercase, and they mean the same thing no matter the case\&.
642 .RE
643 .PP
644 \fI[<branchname>]@{push}\fR, e\&.g\&. \fImaster@{push}\fR, \fI@{push}\fR
645 .RS 4
646 The suffix
647 \fI@{push}\fR
648 reports the branch "where we would push to" if
649 \fBgit push\fR
650 were run while
651 \fBbranchname\fR
652 was checked out (or the current
653 \fBHEAD\fR
654 if no branchname is specified)\&. Since our push destination is in a remote repository, of course, we report the local tracking branch that corresponds to that branch (i\&.e\&., something in
655 \fBrefs/remotes/\fR)\&.
656 .sp
657 Here\(cqs an example to make it more clear:
658 .sp
659 .if n \{\
660 .RS 4
661 .\}
662 .nf
663 $ git config push\&.default current
664 $ git config remote\&.pushdefault myfork
665 $ git switch \-c mybranch origin/master
667 $ git rev\-parse \-\-symbolic\-full\-name @{upstream}
668 refs/remotes/origin/master
670 $ git rev\-parse \-\-symbolic\-full\-name @{push}
671 refs/remotes/myfork/mybranch
672 .fi
673 .if n \{\
674 .RE
675 .\}
676 .sp
677 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,
678 \fI@{push}\fR
679 is the same as
680 \fI@{upstream}\fR, and there is no need for it\&.
681 .sp
682 This suffix is also accepted when spelled in uppercase, and means the same thing no matter the case\&.
683 .RE
684 .PP
685 \fI<rev>^[<n>]\fR, e\&.g\&. \fIHEAD^, v1\&.5\&.1^0\fR
686 .RS 4
687 A suffix
688 \fI^\fR
689 to a revision parameter means the first parent of that commit object\&.
690 \fI^<n>\fR
691 means the <n>th parent (i\&.e\&.
692 \fI<rev>^\fR
693 is equivalent to
694 \fI<rev>^1\fR)\&. As a special rule,
695 \fI<rev>^0\fR
696 means the commit itself and is used when
697 \fI<rev>\fR
698 is the object name of a tag object that refers to a commit object\&.
699 .RE
700 .PP
701 \fI<rev>~[<n>]\fR, e\&.g\&. \fIHEAD~, master~3\fR
702 .RS 4
703 A suffix
704 \fI~\fR
705 to a revision parameter means the first parent of that commit object\&. A suffix
706 \fI~<n>\fR
707 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\&.
708 \fI<rev>~3\fR
709 is equivalent to
710 \fI<rev>^^^\fR
711 which is equivalent to
712 \fI<rev>^1^1^1\fR\&. See below for an illustration of the usage of this form\&.
713 .RE
714 .PP
715 \fI<rev>^{<type>}\fR, e\&.g\&. \fIv0\&.99\&.8^{commit}\fR
716 .RS 4
717 A suffix
718 \fI^\fR
719 followed by an object type name enclosed in brace pair means dereference the object at
720 \fI<rev>\fR
721 recursively until an object of type
722 \fI<type>\fR
723 is found or the object cannot be dereferenced anymore (in which case, barf)\&. For example, if
724 \fI<rev>\fR
725 is a commit\-ish,
726 \fI<rev>^{commit}\fR
727 describes the corresponding commit object\&. Similarly, if
728 \fI<rev>\fR
729 is a tree\-ish,
730 \fI<rev>^{tree}\fR
731 describes the corresponding tree object\&.
732 \fI<rev>^0\fR
733 is a short\-hand for
734 \fI<rev>^{commit}\fR\&.
735 .sp
736 \fI<rev>^{object}\fR
737 can be used to make sure
738 \fI<rev>\fR
739 names an object that exists, without requiring
740 \fI<rev>\fR
741 to be a tag, and without dereferencing
742 \fI<rev>\fR; because a tag is already an object, it does not have to be dereferenced even once to get to an object\&.
743 .sp
744 \fI<rev>^{tag}\fR
745 can be used to ensure that
746 \fI<rev>\fR
747 identifies an existing tag object\&.
748 .RE
749 .PP
750 \fI<rev>^{}\fR, e\&.g\&. \fIv0\&.99\&.8^{}\fR
751 .RS 4
752 A suffix
753 \fI^\fR
754 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\&.
755 .RE
756 .PP
757 \fI<rev>^{/<text>}\fR, e\&.g\&. \fIHEAD^{/fix nasty bug}\fR
758 .RS 4
759 A suffix
760 \fI^\fR
761 to a revision parameter, followed by a brace pair that contains a text led by a slash, is the same as the
762 \fI:/fix nasty bug\fR
763 syntax below except that it returns the youngest matching commit which is reachable from the
764 \fI<rev>\fR
765 before
766 \fI^\fR\&.
767 .RE
768 .PP
769 \fI:/<text>\fR, e\&.g\&. \fI:/fix nasty bug\fR
770 .RS 4
771 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\&.
772 \fI:/^foo\fR\&. The special sequence
773 \fI:/!\fR
774 is reserved for modifiers to what is matched\&.
775 \fI:/!\-foo\fR
776 performs a negative match, while
777 \fI:/!!foo\fR
778 matches a literal
779 \fI!\fR
780 character, followed by
781 \fIfoo\fR\&. Any other sequence beginning with
782 \fI:/!\fR
783 is reserved for now\&. Depending on the given text, the shell\(cqs word splitting rules might require additional quoting\&.
784 .RE
785 .PP
786 \fI<rev>:<path>\fR, e\&.g\&. \fIHEAD:README\fR, \fImaster:\&./README\fR
787 .RS 4
788 A suffix
789 \fI:\fR
790 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
791 \fI\&./\fR
792 or
793 \fI\&.\&./\fR
794 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\&.
795 .RE
796 .PP
797 \fI:[<n>:]<path>\fR, e\&.g\&. \fI:0:README\fR, \fI:README\fR
798 .RS 4
799 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\&.
800 .RE
801 .sp
802 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\&.
803 .sp
804 .if n \{\
805 .RS 4
806 .\}
807 .nf
808 G H I J
809 \e / \e /
810 D E F
811 \e | / \e
812 \e | / |
813 \e|/ |
814 B C
815 \e /
816 \e /
817 A
818 .fi
819 .if n \{\
820 .RE
821 .\}
822 .sp
823 .if n \{\
824 .RS 4
825 .\}
826 .nf
827 A = = A^0
828 B = A^ = A^1 = A~1
829 C = = A^2
830 D = A^^ = A^1^1 = A~2
831 E = B^2 = A^^2
832 F = B^3 = A^^3
833 G = A^^^ = A^1^1^1 = A~3
834 H = D^2 = B^^2 = A^^^2 = A~2^2
835 I = F^ = B^3^ = A^^3^
836 J = F^2 = B^3^2 = A^^3^2
837 .fi
838 .if n \{\
839 .RE
840 .\}
841 .SH "SPECIFYING RANGES"
842 .sp
843 History traversing commands such as \fBgit log\fR operate on a set of commits, not just a single commit\&.
844 .sp
845 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\&.
846 .sp
847 Specifying several revisions means the set of commits reachable from any of the given commits\&.
848 .sp
849 A commit\(cqs reachable set is the commit itself and the commits in its ancestry chain\&.
850 .sp
851 There are several notations to specify a set of connected commits (called a "revision range"), illustrated below\&.
852 .SS "Commit Exclusions"
853 .PP
854 \fI^<rev>\fR (caret) Notation
855 .RS 4
856 To exclude commits reachable from a commit, a prefix
857 \fI^\fR
858 notation is used\&. E\&.g\&.
859 \fI^r1 r2\fR
860 means commits reachable from
861 \fIr2\fR
862 but exclude the ones reachable from
863 \fIr1\fR
864 (i\&.e\&.
865 \fIr1\fR
866 and its ancestors)\&.
867 .RE
868 .SS "Dotted Range Notations"
869 .PP
870 The \fI\&.\&.\fR (two\-dot) Range Notation
871 .RS 4
872 The
873 \fI^r1 r2\fR
874 set operation appears so often that there is a shorthand for it\&. When you have two commits
875 \fIr1\fR
876 and
877 \fIr2\fR
878 (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
879 \fI^r1 r2\fR
880 and it can be written as
881 \fIr1\&.\&.r2\fR\&.
882 .RE
883 .PP
884 The \fI\&...\fR (three\-dot) Symmetric Difference Notation
885 .RS 4
886 A similar notation
887 \fIr1\&.\&.\&.r2\fR
888 is called symmetric difference of
889 \fIr1\fR
890 and
891 \fIr2\fR
892 and is defined as
893 \fIr1 r2 \-\-not $(git merge\-base \-\-all r1 r2)\fR\&. It is the set of commits that are reachable from either one of
894 \fIr1\fR
895 (left side) or
896 \fIr2\fR
897 (right side) but not from both\&.
898 .RE
899 .sp
900 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\&.
901 .sp
902 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\&.
903 .sp
904 .if n \{\
905 .RS 4
906 .\}
907 .nf
908 $ git log A\&.\&.B C\&.\&.D
909 .fi
910 .if n \{\
911 .RE
912 .\}
913 .sp
914 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:
915 .sp
916 .if n \{\
917 .RS 4
918 .\}
919 .nf
920 \-\-\-A\-\-\-B\-\-\-o\-\-\-o\-\-\-C\-\-\-D
921 .fi
922 .if n \{\
923 .RE
924 .\}
925 .sp
926 because A and B are reachable from C, the revision range specified by these two dotted ranges is a single commit D\&.
927 .SS "Other <rev>^ Parent Shorthand Notations"
928 .sp
929 Three other shorthands exist, particularly useful for merge commits, for naming a set that is formed by a commit and its parent commits\&.
930 .sp
931 The \fIr1^@\fR notation means all parents of \fIr1\fR\&.
932 .sp
933 The \fIr1^!\fR notation includes commit \fIr1\fR but excludes all of its parents\&. By itself, this notation denotes the single commit \fIr1\fR\&.
934 .sp
935 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)\&.
936 .sp
937 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\&.
938 .SH "REVISION RANGE SUMMARY"
939 .PP
940 \fI<rev>\fR
941 .RS 4
942 Include commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
943 .RE
944 .PP
945 \fI^<rev>\fR
946 .RS 4
947 Exclude commits that are reachable from <rev> (i\&.e\&. <rev> and its ancestors)\&.
948 .RE
949 .PP
950 \fI<rev1>\&.\&.<rev2>\fR
951 .RS 4
952 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
953 \fBHEAD\fR\&.
954 .RE
955 .PP
956 \fI<rev1>\&.\&.\&.<rev2>\fR
957 .RS 4
958 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
959 \fBHEAD\fR\&.
960 .RE
961 .PP
962 \fI<rev>^@\fR, e\&.g\&. \fIHEAD^@\fR
963 .RS 4
964 A suffix
965 \fI^\fR
966 followed by an at sign is the same as listing all parents of
967 \fI<rev>\fR
968 (meaning, include anything reachable from its parents, but not the commit itself)\&.
969 .RE
970 .PP
971 \fI<rev>^!\fR, e\&.g\&. \fIHEAD^!\fR
972 .RS 4
973 A suffix
974 \fI^\fR
975 followed by an exclamation mark is the same as giving commit
976 \fI<rev>\fR
977 and then all its parents prefixed with
978 \fI^\fR
979 to exclude them (and their ancestors)\&.
980 .RE
981 .PP
982 \fI<rev>^\-<n>\fR, e\&.g\&. \fIHEAD^\-, HEAD^\-2\fR
983 .RS 4
984 Equivalent to
985 \fI<rev>^<n>\&.\&.<rev>\fR, with
986 \fI<n>\fR
987 = 1 if not given\&.
988 .RE
989 .sp
990 Here are a handful of examples using the Loeliger illustration above, with each step in the notation\(cqs expansion and selection carefully spelt out:
991 .sp
992 .if n \{\
993 .RS 4
994 .\}
995 .nf
996 Args Expanded arguments Selected commits
997 D G H D
998 D F G H I J D F
999 ^G D H D
1000 ^D B E I J F B
1001 ^D B C E I J F B C
1002 C I J F C
1003 B\&.\&.C = ^B C C
1004 B\&.\&.\&.C = B ^F C G H D E B C
1005 B^\- = B^\&.\&.B
1006 = ^B^1 B E I J F B
1007 C^@ = C^1
1008 = F I J F
1009 B^@ = B^1 B^2 B^3
1010 = D E F D G H E F I J
1011 C^! = C ^C^@
1012 = C ^C^1
1013 = C ^F C
1014 B^! = B ^B^@
1015 = B ^B^1 ^B^2 ^B^3
1016 = B ^D ^E ^F B
1017 F^! D = F ^I ^J D G H D F
1018 .fi
1019 .if n \{\
1020 .RE
1021 .\}
1022 .SH "PARSEOPT"
1023 .sp
1024 In \fB\-\-parseopt\fR mode, \fIgit rev\-parse\fR helps massaging options to bring to shell scripts the same facilities C builtins have\&. It works as an option normalizer (e\&.g\&. splits single switches aggregate values), a bit like \fBgetopt(1)\fR does\&.
1025 .sp
1026 It takes on the standard input the specification of the options to parse and understand, and echoes on the standard output a string suitable for \fBsh(1)\fR \fBeval\fR to replace the arguments with normalized ones\&. In case of error, it outputs usage on the standard error stream, and exits with code 129\&.
1027 .sp
1028 Note: Make sure you quote the result when passing it to \fBeval\fR\&. See below for an example\&.
1029 .SS "Input Format"
1030 .sp
1031 \fIgit rev\-parse \-\-parseopt\fR input format is fully text based\&. It has two parts, separated by a line that contains only \fB\-\-\fR\&. The lines before the separator (should be one or more) are used for the usage\&. The lines after the separator describe the options\&.
1032 .sp
1033 Each line of options has this format:
1034 .sp
1035 .if n \{\
1036 .RS 4
1037 .\}
1038 .nf
1039 <opt\-spec><flags>*<arg\-hint>? SP+ help LF
1040 .fi
1041 .if n \{\
1042 .RE
1043 .\}
1044 .sp
1046 .PP
1047 \fB<opt\-spec>\fR
1048 .RS 4
1049 its format is the short option character, then the long option name separated by a comma\&. Both parts are not required, though at least one is necessary\&. May not contain any of the
1050 \fB<flags>\fR
1051 characters\&.
1052 \fBh,help\fR,
1053 \fBdry\-run\fR
1054 and
1055 \fBf\fR
1056 are examples of correct
1057 \fB<opt\-spec>\fR\&.
1058 .RE
1059 .PP
1060 \fB<flags>\fR
1061 .RS 4
1062 \fB<flags>\fR
1063 are of
1064 \fB*\fR,
1065 \fB=\fR,
1066 \fB?\fR
1067 or
1068 \fB!\fR\&.
1069 .sp
1070 .RS 4
1071 .ie n \{\
1072 \h'-04'\(bu\h'+03'\c
1073 .\}
1074 .el \{\
1075 .sp -1
1076 .IP \(bu 2.3
1077 .\}
1078 Use
1079 \fB=\fR
1080 if the option takes an argument\&.
1081 .RE
1082 .sp
1083 .RS 4
1084 .ie n \{\
1085 \h'-04'\(bu\h'+03'\c
1086 .\}
1087 .el \{\
1088 .sp -1
1089 .IP \(bu 2.3
1090 .\}
1091 Use
1092 \fB?\fR
1093 to mean that the option takes an optional argument\&. You probably want to use the
1094 \fB\-\-stuck\-long\fR
1095 mode to be able to unambiguously parse the optional argument\&.
1096 .RE
1097 .sp
1098 .RS 4
1099 .ie n \{\
1100 \h'-04'\(bu\h'+03'\c
1101 .\}
1102 .el \{\
1103 .sp -1
1104 .IP \(bu 2.3
1105 .\}
1106 Use
1107 \fB*\fR
1108 to mean that this option should not be listed in the usage generated for the
1109 \fB\-h\fR
1110 argument\&. It\(cqs shown for
1111 \fB\-\-help\-all\fR
1112 as documented in
1113 \fBgitcli\fR(7)\&.
1114 .RE
1115 .sp
1116 .RS 4
1117 .ie n \{\
1118 \h'-04'\(bu\h'+03'\c
1119 .\}
1120 .el \{\
1121 .sp -1
1122 .IP \(bu 2.3
1123 .\}
1124 Use
1125 \fB!\fR
1126 to not make the corresponding negated long option available\&.
1127 .RE
1128 .RE
1129 .PP
1130 \fB<arg\-hint>\fR
1131 .RS 4
1132 \fB<arg\-hint>\fR, if specified, is used as a name of the argument in the help output, for options that take arguments\&.
1133 \fB<arg\-hint>\fR
1134 is terminated by the first whitespace\&. It is customary to use a dash to separate words in a multi\-word argument hint\&.
1135 .RE
1136 .sp
1137 The remainder of the line, after stripping the spaces, is used as the help associated to the option\&.
1138 .sp
1139 Blank lines are ignored, and lines that don\(cqt match this specification are used as option group headers (start the line with a space to create such lines on purpose)\&.
1140 .SS "Example"
1141 .sp
1142 .if n \{\
1143 .RS 4
1144 .\}
1145 .nf
1146 OPTS_SPEC="\e
1147 some\-command [<options>] <args>\&.\&.\&.
1149 some\-command does foo and bar!
1150 \-\-
1151 h,help show the help
1153 foo some nifty option \-\-foo
1154 bar= some cool option \-\-bar with an argument
1155 baz=arg another cool option \-\-baz with a named argument
1156 qux?path qux may take a path argument but has meaning by itself
1158 An option group Header
1159 C? option C with an optional argument"
1161 eval "$(echo "$OPTS_SPEC" | git rev\-parse \-\-parseopt \-\- "$@" || echo exit $?)"
1162 .fi
1163 .if n \{\
1164 .RE
1165 .\}
1166 .sp
1167 .SS "Usage text"
1168 .sp
1169 When \fB"$@"\fR is \fB\-h\fR or \fB\-\-help\fR in the above example, the following usage text would be shown:
1170 .sp
1171 .if n \{\
1172 .RS 4
1173 .\}
1174 .nf
1175 usage: some\-command [<options>] <args>\&.\&.\&.
1177 some\-command does foo and bar!
1179 \-h, \-\-help show the help
1180 \-\-foo some nifty option \-\-foo
1181 \-\-bar \&.\&.\&. some cool option \-\-bar with an argument
1182 \-\-baz <arg> another cool option \-\-baz with a named argument
1183 \-\-qux[=<path>] qux may take a path argument but has meaning by itself
1185 An option group Header
1186 \-C[\&.\&.\&.] option C with an optional argument
1187 .fi
1188 .if n \{\
1189 .RE
1190 .\}
1191 .sp
1192 .SH "SQ\-QUOTE"
1193 .sp
1194 In \fB\-\-sq\-quote\fR mode, \fIgit rev\-parse\fR echoes on the standard output a single line suitable for \fBsh(1)\fR \fBeval\fR\&. This line is made by normalizing the arguments following \fB\-\-sq\-quote\fR\&. Nothing other than quoting the arguments is done\&.
1195 .sp
1196 If you want command input to still be interpreted as usual by \fIgit rev\-parse\fR before the output is shell quoted, see the \fB\-\-sq\fR option\&.
1197 .SS "Example"
1198 .sp
1199 .if n \{\
1200 .RS 4
1201 .\}
1202 .nf
1203 $ cat >your\-git\-script\&.sh <<\eEOF
1204 #!/bin/sh
1205 args=$(git rev\-parse \-\-sq\-quote "$@") # quote user\-supplied arguments
1206 command="git frotz \-n24 $args" # and use it inside a handcrafted
1207 # command line
1208 eval "$command"
1209 EOF
1211 $ sh your\-git\-script\&.sh "a b\(aqc"
1212 .fi
1213 .if n \{\
1214 .RE
1215 .\}
1216 .sp
1217 .SH "EXAMPLES"
1218 .sp
1219 .RS 4
1220 .ie n \{\
1221 \h'-04'\(bu\h'+03'\c
1222 .\}
1223 .el \{\
1224 .sp -1
1225 .IP \(bu 2.3
1226 .\}
1227 Print the object name of the current commit:
1228 .sp
1229 .if n \{\
1230 .RS 4
1231 .\}
1232 .nf
1233 $ git rev\-parse \-\-verify HEAD
1234 .fi
1235 .if n \{\
1236 .RE
1237 .\}
1238 .sp
1239 .RE
1240 .sp
1241 .RS 4
1242 .ie n \{\
1243 \h'-04'\(bu\h'+03'\c
1244 .\}
1245 .el \{\
1246 .sp -1
1247 .IP \(bu 2.3
1248 .\}
1249 Print the commit object name from the revision in the $REV shell variable:
1250 .sp
1251 .if n \{\
1252 .RS 4
1253 .\}
1254 .nf
1255 $ git rev\-parse \-\-verify \-\-end\-of\-options $REV^{commit}
1256 .fi
1257 .if n \{\
1258 .RE
1259 .\}
1260 .sp
1261 This will error out if $REV is empty or not a valid revision\&.
1262 .RE
1263 .sp
1264 .RS 4
1265 .ie n \{\
1266 \h'-04'\(bu\h'+03'\c
1267 .\}
1268 .el \{\
1269 .sp -1
1270 .IP \(bu 2.3
1271 .\}
1272 Similar to above:
1273 .sp
1274 .if n \{\
1275 .RS 4
1276 .\}
1277 .nf
1278 $ git rev\-parse \-\-default master \-\-verify \-\-end\-of\-options $REV
1279 .fi
1280 .if n \{\
1281 .RE
1282 .\}
1283 .sp
1284 but if $REV is empty, the commit object name from master will be printed\&.
1285 .RE
1286 .SH "GIT"
1287 .sp
1288 Part of the \fBgit\fR(1) suite