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