]>
Commit | Line | Data |
---|---|---|
7fc9d69f JH |
1 | git-rev-parse(1) |
2 | ================ | |
3 | ||
4 | NAME | |
5 | ---- | |
7bd7f280 | 6 | git-rev-parse - Pick out and massage parameters |
7fc9d69f JH |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
b1889c36 | 11 | 'git rev-parse' [ --option ] <args>... |
7fc9d69f JH |
12 | |
13 | DESCRIPTION | |
14 | ----------- | |
5077fa9c | 15 | |
abda1ef5 | 16 | Many git porcelainish commands take mixture of flags |
5077fa9c | 17 | (i.e. parameters that begin with a dash '-') and parameters |
0b444cdb | 18 | meant for the underlying 'git rev-list' command they use internally |
483bc4f0 | 19 | and flags and parameters for the other commands they use |
0b444cdb | 20 | downstream of 'git rev-list'. This command is used to |
5077fa9c | 21 | distinguish between them. |
7fc9d69f JH |
22 | |
23 | ||
24 | OPTIONS | |
25 | ------- | |
21d47835 | 26 | --parseopt:: |
0b444cdb | 27 | Use 'git rev-parse' in option parsing mode (see PARSEOPT section below). |
21d47835 | 28 | |
2163e3f7 | 29 | --keep-dashdash:: |
21d47835 PH |
30 | Only meaningful in `--parseopt` mode. Tells the option parser to echo |
31 | out the first `--` met instead of skipping it. | |
32 | ||
6e0800ef UKK |
33 | --stop-at-non-option:: |
34 | Only meaningful in `--parseopt` mode. Lets the option parser stop at | |
35 | the first non-option argument. This can be used to parse sub-commands | |
6a5d0b0a | 36 | that take options themselves. |
6e0800ef | 37 | |
50325377 | 38 | --sq-quote:: |
0b444cdb | 39 | Use 'git rev-parse' in shell quoting mode (see SQ-QUOTE |
50325377 CC |
40 | section below). In contrast to the `--sq` option below, this |
41 | mode does only quoting. Nothing else is done to command input. | |
42 | ||
5077fa9c JH |
43 | --revs-only:: |
44 | Do not output flags and parameters not meant for | |
0b444cdb | 45 | 'git rev-list' command. |
5077fa9c JH |
46 | |
47 | --no-revs:: | |
48 | Do not output flags and parameters meant for | |
0b444cdb | 49 | 'git rev-list' command. |
5077fa9c JH |
50 | |
51 | --flags:: | |
52 | Do not output non-flag parameters. | |
53 | ||
54 | --no-flags:: | |
55 | Do not output flag parameters. | |
56 | ||
57 | --default <arg>:: | |
58 | If there is no parameter given by the user, use `<arg>` | |
59 | instead. | |
60 | ||
61 | --verify:: | |
62 | The parameter given must be usable as a single, valid | |
63 | object name. Otherwise barf and abort. | |
64 | ||
3240240f SB |
65 | -q:: |
66 | --quiet:: | |
b1b35969 CC |
67 | Only meaningful in `--verify` mode. Do not output an error |
68 | message if the first argument is not a valid object name; | |
69 | instead exit with non-zero status silently. | |
70 | ||
5077fa9c JH |
71 | --sq:: |
72 | Usually the output is made one line per flag and | |
73 | parameter. This option makes output a single line, | |
74 | properly quoted for consumption by shell. Useful when | |
75 | you expect your parameter to contain whitespaces and | |
76 | newlines (e.g. when using pickaxe `-S` with | |
4cacbf67 | 77 | 'git diff-{asterisk}'). In contrast to the `--sq-quote` option, |
50325377 | 78 | the command input is still interpreted as usual. |
5077fa9c JH |
79 | |
80 | --not:: | |
babfaba2 JF |
81 | When showing object names, prefix them with '{caret}' and |
82 | strip '{caret}' prefix from the object names that already have | |
5077fa9c JH |
83 | one. |
84 | ||
85 | --symbolic:: | |
86 | Usually the object names are output in SHA1 form (with | |
babfaba2 | 87 | possible '{caret}' prefix); this option makes them output in a |
5077fa9c JH |
88 | form as close to the original input as possible. |
89 | ||
a6d97d49 JH |
90 | --symbolic-full-name:: |
91 | This is similar to \--symbolic, but it omits input that | |
92 | are not refs (i.e. branch or tag names; or more | |
93 | explicitly disambiguating "heads/master" form, when you | |
94 | want to name the "master" branch when there is an | |
95 | unfortunately named tag "master"), and show them as full | |
96 | refnames (e.g. "refs/heads/master"). | |
5077fa9c | 97 | |
0adda936 | 98 | --abbrev-ref[=(strict|loose)]:: |
a45d3469 BW |
99 | A non-ambiguous short name of the objects name. |
100 | The option core.warnAmbiguousRefs is used to select the strict | |
101 | abbreviation mode. | |
102 | ||
5077fa9c | 103 | --all:: |
cc1b8d8b | 104 | Show all refs found in `refs/`. |
5077fa9c | 105 | |
b09fe971 | 106 | --branches[=pattern]:: |
b09fe971 | 107 | --tags[=pattern]:: |
b09fe971 | 108 | --remotes[=pattern]:: |
e2b53e58 | 109 | Show all branches, tags, or remote-tracking branches, |
cc1b8d8b JK |
110 | respectively (i.e., refs found in `refs/heads`, |
111 | `refs/tags`, or `refs/remotes`, respectively). | |
e2b53e58 TR |
112 | + |
113 | If a `pattern` is given, only refs matching the given shell glob are | |
114 | shown. If the pattern does not contain a globbing character (`?`, | |
4cacbf67 JN |
115 | `{asterisk}`, or `[`), it is turned into a prefix match by |
116 | appending `/{asterisk}`. | |
e2b53e58 TR |
117 | |
118 | --glob=pattern:: | |
119 | Show all refs matching the shell glob pattern `pattern`. If | |
120 | the pattern does not start with `refs/`, this is automatically | |
121 | prepended. If the pattern does not contain a globbing | |
4cacbf67 JN |
122 | character (`?`, `{asterisk}`, or `[`), it is turned into a prefix |
123 | match by appending `/{asterisk}`. | |
a62be77f | 124 | |
7cceca5c SD |
125 | --show-toplevel:: |
126 | Show the absolute path of the top-level directory. | |
127 | ||
5077fa9c | 128 | --show-prefix:: |
5f94c730 | 129 | When the command is invoked from a subdirectory, show the |
5077fa9c JH |
130 | path of the current directory relative to the top-level |
131 | directory. | |
7fc9d69f | 132 | |
5f94c730 JH |
133 | --show-cdup:: |
134 | When the command is invoked from a subdirectory, show the | |
135 | path of the top-level directory relative to the current | |
136 | directory (typically a sequence of "../", or an empty string). | |
137 | ||
735d80b3 JF |
138 | --git-dir:: |
139 | Show `$GIT_DIR` if defined else show the path to the .git directory. | |
140 | ||
c9bf7be2 | 141 | --is-inside-git-dir:: |
4faac246 ML |
142 | When the current working directory is below the repository |
143 | directory print "true", otherwise "false". | |
144 | ||
892c41b9 ML |
145 | --is-inside-work-tree:: |
146 | When the current working directory is inside the work tree of the | |
147 | repository print "true", otherwise "false". | |
148 | ||
493c774e ML |
149 | --is-bare-repository:: |
150 | When the repository is bare print "true", otherwise "false". | |
c9bf7be2 | 151 | |
94c8ccaa GB |
152 | --local-env-vars:: |
153 | List the GIT_* environment variables that are local to the | |
154 | repository (e.g. GIT_DIR or GIT_WORK_TREE, but not GIT_EDITOR). | |
155 | Only the names of the variables are listed, not their value, | |
156 | even if they are set. | |
157 | ||
3240240f SB |
158 | --short:: |
159 | --short=number:: | |
735d80b3 | 160 | Instead of outputting the full SHA1 values of object names try to |
abda1ef5 | 161 | abbreviate them to a shorter unique name. When no length is specified |
735d80b3 JF |
162 | 7 is used. The minimum length is 4. |
163 | ||
3240240f SB |
164 | --since=datestring:: |
165 | --after=datestring:: | |
483bc4f0 | 166 | Parse the date string, and output the corresponding |
0b444cdb | 167 | --max-age= parameter for 'git rev-list'. |
a3114b34 | 168 | |
3240240f SB |
169 | --until=datestring:: |
170 | --before=datestring:: | |
483bc4f0 | 171 | Parse the date string, and output the corresponding |
0b444cdb | 172 | --min-age= parameter for 'git rev-list'. |
a3114b34 | 173 | |
7fc9d69f | 174 | <args>...:: |
5077fa9c | 175 | Flags and parameters to be parsed. |
7fc9d69f JH |
176 | |
177 | ||
5a8f3117 | 178 | include::revisions.txt[] |
be4c7014 | 179 | |
21d47835 PH |
180 | PARSEOPT |
181 | -------- | |
182 | ||
0b444cdb | 183 | In `--parseopt` mode, 'git rev-parse' helps massaging options to bring to shell |
21d47835 PH |
184 | scripts the same facilities C builtins have. It works as an option normalizer |
185 | (e.g. splits single switches aggregate values), a bit like `getopt(1)` does. | |
186 | ||
187 | It takes on the standard input the specification of the options to parse and | |
ac2e1e63 | 188 | understand, and echoes on the standard output a string suitable for `sh(1)` `eval` |
21d47835 PH |
189 | to replace the arguments with normalized ones. In case of error, it outputs |
190 | usage on the standard error stream, and exits with code 129. | |
191 | ||
ac2e1e63 TR |
192 | Note: Make sure you quote the result when passing it to `eval`. See |
193 | below for an example. | |
194 | ||
21d47835 PH |
195 | Input Format |
196 | ~~~~~~~~~~~~ | |
197 | ||
0b444cdb | 198 | 'git rev-parse --parseopt' input format is fully text based. It has two parts, |
21d47835 PH |
199 | separated by a line that contains only `--`. The lines before the separator |
200 | (should be more than one) are used for the usage. | |
201 | The lines after the separator describe the options. | |
202 | ||
203 | Each line of options has this format: | |
204 | ||
205 | ------------ | |
ff962a3f | 206 | <opt_spec><flags>* SP+ help LF |
21d47835 PH |
207 | ------------ |
208 | ||
209 | `<opt_spec>`:: | |
210 | its format is the short option character, then the long option name | |
211 | separated by a comma. Both parts are not required, though at least one | |
212 | is necessary. `h,help`, `dry-run` and `f` are all three correct | |
213 | `<opt_spec>`. | |
214 | ||
ff962a3f PH |
215 | `<flags>`:: |
216 | `<flags>` are of `*`, `=`, `?` or `!`. | |
217 | * Use `=` if the option takes an argument. | |
218 | ||
219 | * Use `?` to mean that the option is optional (though its use is discouraged). | |
220 | ||
221 | * Use `*` to mean that this option should not be listed in the usage | |
222 | generated for the `-h` argument. It's shown for `--help-all` as | |
a5af0e2c | 223 | documented in linkgit:gitcli[7]. |
ff962a3f PH |
224 | |
225 | * Use `!` to not make the corresponding negated long option available. | |
21d47835 PH |
226 | |
227 | The remainder of the line, after stripping the spaces, is used | |
228 | as the help associated to the option. | |
229 | ||
230 | Blank lines are ignored, and lines that don't match this specification are used | |
231 | as option group headers (start the line with a space to create such | |
232 | lines on purpose). | |
233 | ||
234 | Example | |
235 | ~~~~~~~ | |
236 | ||
237 | ------------ | |
238 | OPTS_SPEC="\ | |
239 | some-command [options] <args>... | |
240 | ||
241 | some-command does foo and bar! | |
242 | -- | |
243 | h,help show the help | |
244 | ||
245 | foo some nifty option --foo | |
246 | bar= some cool option --bar with an argument | |
247 | ||
248 | An option group Header | |
249 | C? option C with an optional argument" | |
250 | ||
ac2e1e63 | 251 | eval "$(echo "$OPTS_SPEC" | git rev-parse --parseopt -- "$@" || echo exit $?)" |
21d47835 PH |
252 | ------------ |
253 | ||
50325377 CC |
254 | SQ-QUOTE |
255 | -------- | |
256 | ||
0b444cdb | 257 | In `--sq-quote` mode, 'git rev-parse' echoes on the standard output a |
50325377 CC |
258 | single line suitable for `sh(1)` `eval`. This line is made by |
259 | normalizing the arguments following `--sq-quote`. Nothing other than | |
260 | quoting the arguments is done. | |
261 | ||
262 | If you want command input to still be interpreted as usual by | |
0b444cdb | 263 | 'git rev-parse' before the output is shell quoted, see the `--sq` |
50325377 CC |
264 | option. |
265 | ||
266 | Example | |
267 | ~~~~~~~ | |
268 | ||
269 | ------------ | |
270 | $ cat >your-git-script.sh <<\EOF | |
271 | #!/bin/sh | |
272 | args=$(git rev-parse --sq-quote "$@") # quote user-supplied arguments | |
273 | command="git frotz -n24 $args" # and use it inside a handcrafted | |
274 | # command line | |
275 | eval "$command" | |
276 | EOF | |
277 | ||
278 | $ sh your-git-script.sh "a b'c" | |
279 | ------------ | |
280 | ||
824b5dc2 CC |
281 | EXAMPLES |
282 | -------- | |
283 | ||
284 | * Print the object name of the current commit: | |
285 | + | |
286 | ------------ | |
287 | $ git rev-parse --verify HEAD | |
288 | ------------ | |
289 | ||
290 | * Print the commit object name from the revision in the $REV shell variable: | |
291 | + | |
292 | ------------ | |
293 | $ git rev-parse --verify $REV | |
294 | ------------ | |
295 | + | |
296 | This will error out if $REV is empty or not a valid revision. | |
297 | ||
298 | * Same as above: | |
299 | + | |
300 | ------------ | |
301 | $ git rev-parse --default master --verify $REV | |
302 | ------------ | |
303 | + | |
304 | but if $REV is empty, the commit object name from master will be printed. | |
305 | ||
21d47835 | 306 | |
7fc9d69f JH |
307 | Author |
308 | ------ | |
21d47835 | 309 | Written by Linus Torvalds <torvalds@osdl.org> . |
59eb68aa | 310 | Junio C Hamano <gitster@pobox.com> and Pierre Habouzit <madcoder@debian.org> |
7fc9d69f JH |
311 | |
312 | Documentation | |
313 | -------------- | |
314 | Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>. | |
315 | ||
316 | GIT | |
317 | --- | |
9e1f0a85 | 318 | Part of the linkgit:git[1] suite |