6 git - the stupid content tracker
12 'git' [--version] [--help] [-C <path>] [-c <name>=<value>]
13 [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
14 [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
15 [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
20 Git is a fast, scalable, distributed revision control system with an
21 unusually rich command set that provides both high-level operations
22 and full access to internals.
24 See linkgit:gittutorial[7] to get started, then see
25 link:everyday.html[Everyday Git] for a useful minimum set of
26 commands. The link:user-manual.html[Git User's Manual] has a more
27 in-depth introduction.
29 After you mastered the basic concepts, you can come back to this
30 page to learn what commands Git offers. You can learn more about
31 individual Git commands with "git help command". linkgit:gitcli[7]
32 manual page gives you an overview of the command-line command syntax.
34 Formatted and hyperlinked version of the latest Git documentation
35 can be viewed at `http://git-htmldocs.googlecode.com/git/git.html`.
41 You are reading the documentation for the latest (possibly
42 unreleased) version of Git, that is available from the 'master'
43 branch of the `git.git` repository.
44 Documentation for older releases are available here:
46 * link:v2.1.3/git.html[documentation for release 2.1.3]
49 link:RelNotes/2.1.3.txt[2.1.3],
50 link:RelNotes/2.1.2.txt[2.1.2],
51 link:RelNotes/2.1.1.txt[2.1.1],
52 link:RelNotes/2.1.0.txt[2.1].
54 * link:v2.0.5/git.html[documentation for release 2.0.5]
57 link:RelNotes/2.0.5.txt[2.0.5],
58 link:RelNotes/2.0.4.txt[2.0.4],
59 link:RelNotes/2.0.3.txt[2.0.3],
60 link:RelNotes/2.0.2.txt[2.0.2],
61 link:RelNotes/2.0.1.txt[2.0.1],
62 link:RelNotes/2.0.0.txt[2.0.0].
64 * link:v1.9.5/git.html[documentation for release 1.9.5]
67 link:RelNotes/1.9.5.txt[1.9.5],
68 link:RelNotes/1.9.4.txt[1.9.4],
69 link:RelNotes/1.9.3.txt[1.9.3],
70 link:RelNotes/1.9.2.txt[1.9.2],
71 link:RelNotes/1.9.1.txt[1.9.1],
72 link:RelNotes/1.9.0.txt[1.9.0].
74 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
77 link:RelNotes/1.8.5.6.txt[1.8.5.6],
78 link:RelNotes/1.8.5.5.txt[1.8.5.5],
79 link:RelNotes/1.8.5.4.txt[1.8.5.4],
80 link:RelNotes/1.8.5.3.txt[1.8.5.3],
81 link:RelNotes/1.8.5.2.txt[1.8.5.2],
82 link:RelNotes/1.8.5.1.txt[1.8.5.1],
83 link:RelNotes/1.8.5.txt[1.8.5].
85 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
88 link:RelNotes/1.8.4.5.txt[1.8.4.5],
89 link:RelNotes/1.8.4.4.txt[1.8.4.4],
90 link:RelNotes/1.8.4.3.txt[1.8.4.3],
91 link:RelNotes/1.8.4.2.txt[1.8.4.2],
92 link:RelNotes/1.8.4.1.txt[1.8.4.1],
93 link:RelNotes/1.8.4.txt[1.8.4].
95 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
98 link:RelNotes/1.8.3.4.txt[1.8.3.4],
99 link:RelNotes/1.8.3.3.txt[1.8.3.3],
100 link:RelNotes/1.8.3.2.txt[1.8.3.2],
101 link:RelNotes/1.8.3.1.txt[1.8.3.1],
102 link:RelNotes/1.8.3.txt[1.8.3].
104 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
107 link:RelNotes/1.8.2.3.txt[1.8.2.3],
108 link:RelNotes/1.8.2.2.txt[1.8.2.2],
109 link:RelNotes/1.8.2.1.txt[1.8.2.1],
110 link:RelNotes/1.8.2.txt[1.8.2].
112 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
115 link:RelNotes/1.8.1.6.txt[1.8.1.6],
116 link:RelNotes/1.8.1.5.txt[1.8.1.5],
117 link:RelNotes/1.8.1.4.txt[1.8.1.4],
118 link:RelNotes/1.8.1.3.txt[1.8.1.3],
119 link:RelNotes/1.8.1.2.txt[1.8.1.2],
120 link:RelNotes/1.8.1.1.txt[1.8.1.1],
121 link:RelNotes/1.8.1.txt[1.8.1].
123 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
126 link:RelNotes/1.8.0.3.txt[1.8.0.3],
127 link:RelNotes/1.8.0.2.txt[1.8.0.2],
128 link:RelNotes/1.8.0.1.txt[1.8.0.1],
129 link:RelNotes/1.8.0.txt[1.8.0].
131 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
134 link:RelNotes/1.7.12.4.txt[1.7.12.4],
135 link:RelNotes/1.7.12.3.txt[1.7.12.3],
136 link:RelNotes/1.7.12.2.txt[1.7.12.2],
137 link:RelNotes/1.7.12.1.txt[1.7.12.1],
138 link:RelNotes/1.7.12.txt[1.7.12].
140 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
143 link:RelNotes/1.7.11.7.txt[1.7.11.7],
144 link:RelNotes/1.7.11.6.txt[1.7.11.6],
145 link:RelNotes/1.7.11.5.txt[1.7.11.5],
146 link:RelNotes/1.7.11.4.txt[1.7.11.4],
147 link:RelNotes/1.7.11.3.txt[1.7.11.3],
148 link:RelNotes/1.7.11.2.txt[1.7.11.2],
149 link:RelNotes/1.7.11.1.txt[1.7.11.1],
150 link:RelNotes/1.7.11.txt[1.7.11].
152 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
155 link:RelNotes/1.7.10.5.txt[1.7.10.5],
156 link:RelNotes/1.7.10.4.txt[1.7.10.4],
157 link:RelNotes/1.7.10.3.txt[1.7.10.3],
158 link:RelNotes/1.7.10.2.txt[1.7.10.2],
159 link:RelNotes/1.7.10.1.txt[1.7.10.1],
160 link:RelNotes/1.7.10.txt[1.7.10].
162 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
165 link:RelNotes/1.7.9.7.txt[1.7.9.7],
166 link:RelNotes/1.7.9.6.txt[1.7.9.6],
167 link:RelNotes/1.7.9.5.txt[1.7.9.5],
168 link:RelNotes/1.7.9.4.txt[1.7.9.4],
169 link:RelNotes/1.7.9.3.txt[1.7.9.3],
170 link:RelNotes/1.7.9.2.txt[1.7.9.2],
171 link:RelNotes/1.7.9.1.txt[1.7.9.1],
172 link:RelNotes/1.7.9.txt[1.7.9].
174 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
177 link:RelNotes/1.7.8.6.txt[1.7.8.6],
178 link:RelNotes/1.7.8.5.txt[1.7.8.5],
179 link:RelNotes/1.7.8.4.txt[1.7.8.4],
180 link:RelNotes/1.7.8.3.txt[1.7.8.3],
181 link:RelNotes/1.7.8.2.txt[1.7.8.2],
182 link:RelNotes/1.7.8.1.txt[1.7.8.1],
183 link:RelNotes/1.7.8.txt[1.7.8].
185 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
188 link:RelNotes/1.7.7.7.txt[1.7.7.7],
189 link:RelNotes/1.7.7.6.txt[1.7.7.6],
190 link:RelNotes/1.7.7.5.txt[1.7.7.5],
191 link:RelNotes/1.7.7.4.txt[1.7.7.4],
192 link:RelNotes/1.7.7.3.txt[1.7.7.3],
193 link:RelNotes/1.7.7.2.txt[1.7.7.2],
194 link:RelNotes/1.7.7.1.txt[1.7.7.1],
195 link:RelNotes/1.7.7.txt[1.7.7].
197 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
200 link:RelNotes/1.7.6.6.txt[1.7.6.6],
201 link:RelNotes/1.7.6.5.txt[1.7.6.5],
202 link:RelNotes/1.7.6.4.txt[1.7.6.4],
203 link:RelNotes/1.7.6.3.txt[1.7.6.3],
204 link:RelNotes/1.7.6.2.txt[1.7.6.2],
205 link:RelNotes/1.7.6.1.txt[1.7.6.1],
206 link:RelNotes/1.7.6.txt[1.7.6].
208 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
211 link:RelNotes/1.7.5.4.txt[1.7.5.4],
212 link:RelNotes/1.7.5.3.txt[1.7.5.3],
213 link:RelNotes/1.7.5.2.txt[1.7.5.2],
214 link:RelNotes/1.7.5.1.txt[1.7.5.1],
215 link:RelNotes/1.7.5.txt[1.7.5].
217 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
220 link:RelNotes/1.7.4.5.txt[1.7.4.5],
221 link:RelNotes/1.7.4.4.txt[1.7.4.4],
222 link:RelNotes/1.7.4.3.txt[1.7.4.3],
223 link:RelNotes/1.7.4.2.txt[1.7.4.2],
224 link:RelNotes/1.7.4.1.txt[1.7.4.1],
225 link:RelNotes/1.7.4.txt[1.7.4].
227 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
230 link:RelNotes/1.7.3.5.txt[1.7.3.5],
231 link:RelNotes/1.7.3.4.txt[1.7.3.4],
232 link:RelNotes/1.7.3.3.txt[1.7.3.3],
233 link:RelNotes/1.7.3.2.txt[1.7.3.2],
234 link:RelNotes/1.7.3.1.txt[1.7.3.1],
235 link:RelNotes/1.7.3.txt[1.7.3].
237 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
240 link:RelNotes/1.7.2.5.txt[1.7.2.5],
241 link:RelNotes/1.7.2.4.txt[1.7.2.4],
242 link:RelNotes/1.7.2.3.txt[1.7.2.3],
243 link:RelNotes/1.7.2.2.txt[1.7.2.2],
244 link:RelNotes/1.7.2.1.txt[1.7.2.1],
245 link:RelNotes/1.7.2.txt[1.7.2].
247 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
250 link:RelNotes/1.7.1.4.txt[1.7.1.4],
251 link:RelNotes/1.7.1.3.txt[1.7.1.3],
252 link:RelNotes/1.7.1.2.txt[1.7.1.2],
253 link:RelNotes/1.7.1.1.txt[1.7.1.1],
254 link:RelNotes/1.7.1.txt[1.7.1].
256 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
259 link:RelNotes/1.7.0.9.txt[1.7.0.9],
260 link:RelNotes/1.7.0.8.txt[1.7.0.8],
261 link:RelNotes/1.7.0.7.txt[1.7.0.7],
262 link:RelNotes/1.7.0.6.txt[1.7.0.6],
263 link:RelNotes/1.7.0.5.txt[1.7.0.5],
264 link:RelNotes/1.7.0.4.txt[1.7.0.4],
265 link:RelNotes/1.7.0.3.txt[1.7.0.3],
266 link:RelNotes/1.7.0.2.txt[1.7.0.2],
267 link:RelNotes/1.7.0.1.txt[1.7.0.1],
268 link:RelNotes/1.7.0.txt[1.7.0].
270 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
273 link:RelNotes/1.6.6.3.txt[1.6.6.3],
274 link:RelNotes/1.6.6.2.txt[1.6.6.2],
275 link:RelNotes/1.6.6.1.txt[1.6.6.1],
276 link:RelNotes/1.6.6.txt[1.6.6].
278 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
281 link:RelNotes/1.6.5.9.txt[1.6.5.9],
282 link:RelNotes/1.6.5.8.txt[1.6.5.8],
283 link:RelNotes/1.6.5.7.txt[1.6.5.7],
284 link:RelNotes/1.6.5.6.txt[1.6.5.6],
285 link:RelNotes/1.6.5.5.txt[1.6.5.5],
286 link:RelNotes/1.6.5.4.txt[1.6.5.4],
287 link:RelNotes/1.6.5.3.txt[1.6.5.3],
288 link:RelNotes/1.6.5.2.txt[1.6.5.2],
289 link:RelNotes/1.6.5.1.txt[1.6.5.1],
290 link:RelNotes/1.6.5.txt[1.6.5].
292 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
295 link:RelNotes/1.6.4.5.txt[1.6.4.5],
296 link:RelNotes/1.6.4.4.txt[1.6.4.4],
297 link:RelNotes/1.6.4.3.txt[1.6.4.3],
298 link:RelNotes/1.6.4.2.txt[1.6.4.2],
299 link:RelNotes/1.6.4.1.txt[1.6.4.1],
300 link:RelNotes/1.6.4.txt[1.6.4].
302 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
305 link:RelNotes/1.6.3.4.txt[1.6.3.4],
306 link:RelNotes/1.6.3.3.txt[1.6.3.3],
307 link:RelNotes/1.6.3.2.txt[1.6.3.2],
308 link:RelNotes/1.6.3.1.txt[1.6.3.1],
309 link:RelNotes/1.6.3.txt[1.6.3].
312 link:RelNotes/1.6.2.5.txt[1.6.2.5],
313 link:RelNotes/1.6.2.4.txt[1.6.2.4],
314 link:RelNotes/1.6.2.3.txt[1.6.2.3],
315 link:RelNotes/1.6.2.2.txt[1.6.2.2],
316 link:RelNotes/1.6.2.1.txt[1.6.2.1],
317 link:RelNotes/1.6.2.txt[1.6.2].
319 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
322 link:RelNotes/1.6.1.3.txt[1.6.1.3],
323 link:RelNotes/1.6.1.2.txt[1.6.1.2],
324 link:RelNotes/1.6.1.1.txt[1.6.1.1],
325 link:RelNotes/1.6.1.txt[1.6.1].
327 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
330 link:RelNotes/1.6.0.6.txt[1.6.0.6],
331 link:RelNotes/1.6.0.5.txt[1.6.0.5],
332 link:RelNotes/1.6.0.4.txt[1.6.0.4],
333 link:RelNotes/1.6.0.3.txt[1.6.0.3],
334 link:RelNotes/1.6.0.2.txt[1.6.0.2],
335 link:RelNotes/1.6.0.1.txt[1.6.0.1],
336 link:RelNotes/1.6.0.txt[1.6.0].
338 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
341 link:RelNotes/1.5.6.6.txt[1.5.6.6],
342 link:RelNotes/1.5.6.5.txt[1.5.6.5],
343 link:RelNotes/1.5.6.4.txt[1.5.6.4],
344 link:RelNotes/1.5.6.3.txt[1.5.6.3],
345 link:RelNotes/1.5.6.2.txt[1.5.6.2],
346 link:RelNotes/1.5.6.1.txt[1.5.6.1],
347 link:RelNotes/1.5.6.txt[1.5.6].
349 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
352 link:RelNotes/1.5.5.6.txt[1.5.5.6],
353 link:RelNotes/1.5.5.5.txt[1.5.5.5],
354 link:RelNotes/1.5.5.4.txt[1.5.5.4],
355 link:RelNotes/1.5.5.3.txt[1.5.5.3],
356 link:RelNotes/1.5.5.2.txt[1.5.5.2],
357 link:RelNotes/1.5.5.1.txt[1.5.5.1],
358 link:RelNotes/1.5.5.txt[1.5.5].
360 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
363 link:RelNotes/1.5.4.7.txt[1.5.4.7],
364 link:RelNotes/1.5.4.6.txt[1.5.4.6],
365 link:RelNotes/1.5.4.5.txt[1.5.4.5],
366 link:RelNotes/1.5.4.4.txt[1.5.4.4],
367 link:RelNotes/1.5.4.3.txt[1.5.4.3],
368 link:RelNotes/1.5.4.2.txt[1.5.4.2],
369 link:RelNotes/1.5.4.1.txt[1.5.4.1],
370 link:RelNotes/1.5.4.txt[1.5.4].
372 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
375 link:RelNotes/1.5.3.8.txt[1.5.3.8],
376 link:RelNotes/1.5.3.7.txt[1.5.3.7],
377 link:RelNotes/1.5.3.6.txt[1.5.3.6],
378 link:RelNotes/1.5.3.5.txt[1.5.3.5],
379 link:RelNotes/1.5.3.4.txt[1.5.3.4],
380 link:RelNotes/1.5.3.3.txt[1.5.3.3],
381 link:RelNotes/1.5.3.2.txt[1.5.3.2],
382 link:RelNotes/1.5.3.1.txt[1.5.3.1],
383 link:RelNotes/1.5.3.txt[1.5.3].
385 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
388 link:RelNotes/1.5.2.5.txt[1.5.2.5],
389 link:RelNotes/1.5.2.4.txt[1.5.2.4],
390 link:RelNotes/1.5.2.3.txt[1.5.2.3],
391 link:RelNotes/1.5.2.2.txt[1.5.2.2],
392 link:RelNotes/1.5.2.1.txt[1.5.2.1],
393 link:RelNotes/1.5.2.txt[1.5.2].
395 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
398 link:RelNotes/1.5.1.6.txt[1.5.1.6],
399 link:RelNotes/1.5.1.5.txt[1.5.1.5],
400 link:RelNotes/1.5.1.4.txt[1.5.1.4],
401 link:RelNotes/1.5.1.3.txt[1.5.1.3],
402 link:RelNotes/1.5.1.2.txt[1.5.1.2],
403 link:RelNotes/1.5.1.1.txt[1.5.1.1],
404 link:RelNotes/1.5.1.txt[1.5.1].
406 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
409 link:RelNotes/1.5.0.7.txt[1.5.0.7],
410 link:RelNotes/1.5.0.6.txt[1.5.0.6],
411 link:RelNotes/1.5.0.5.txt[1.5.0.5],
412 link:RelNotes/1.5.0.3.txt[1.5.0.3],
413 link:RelNotes/1.5.0.2.txt[1.5.0.2],
414 link:RelNotes/1.5.0.1.txt[1.5.0.1],
415 link:RelNotes/1.5.0.txt[1.5.0].
417 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
418 link:v1.3.3/git.html[1.3.3],
419 link:v1.2.6/git.html[1.2.6],
420 link:v1.0.13/git.html[1.0.13].
429 Prints the Git suite version that the 'git' program came from.
432 Prints the synopsis and a list of the most commonly used
433 commands. If the option '--all' or '-a' is given then all
434 available commands are printed. If a Git command is named this
435 option will bring up the manual page for that command.
437 Other options are available to control how the manual page is
438 displayed. See linkgit:git-help[1] for more information,
439 because `git --help ...` is converted internally into `git
443 Run as if git was started in '<path>' instead of the current working
444 directory. When multiple `-C` options are given, each subsequent
445 non-absolute `-C <path>` is interpreted relative to the preceding `-C
448 This option affects options that expect path name like `--git-dir` and
449 `--work-tree` in that their interpretations of the path names would be
450 made relative to the working directory caused by the `-C` option. For
451 example the following invocations are equivalent:
453 git --git-dir=a.git --work-tree=b -C c status
454 git --git-dir=c/a.git --work-tree=c/b status
457 Pass a configuration parameter to the command. The value
458 given will override values from configuration files.
459 The <name> is expected in the same format as listed by
460 'git config' (subkeys separated by dots).
462 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
463 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
464 config file). Including the equals but with an empty value (like `git -c
465 foo.bar= ...`) sets `foo.bar` to the empty string.
467 --exec-path[=<path>]::
468 Path to wherever your core Git programs are installed.
469 This can also be controlled by setting the GIT_EXEC_PATH
470 environment variable. If no path is given, 'git' will print
471 the current setting and then exit.
474 Print the path, without trailing slash, where Git's HTML
475 documentation is installed and exit.
478 Print the manpath (see `man(1)`) for the man pages for
479 this version of Git and exit.
482 Print the path where the Info files documenting this
483 version of Git are installed and exit.
487 Pipe all output into 'less' (or if set, $PAGER) if standard
488 output is a terminal. This overrides the `pager.<cmd>`
489 configuration options (see the "Configuration Mechanism" section
493 Do not pipe Git output into a pager.
496 Set the path to the repository. This can also be controlled by
497 setting the GIT_DIR environment variable. It can be an absolute
498 path or relative path to current working directory.
501 Set the path to the working tree. It can be an absolute path
502 or a path relative to the current working directory.
503 This can also be controlled by setting the GIT_WORK_TREE
504 environment variable and the core.worktree configuration
505 variable (see core.worktree in linkgit:git-config[1] for a
506 more detailed discussion).
509 Set the Git namespace. See linkgit:gitnamespaces[7] for more
510 details. Equivalent to setting the `GIT_NAMESPACE` environment
514 Treat the repository as a bare repository. If GIT_DIR
515 environment is not set, it is set to the current working
518 --no-replace-objects::
519 Do not use replacement refs to replace Git objects. See
520 linkgit:git-replace[1] for more information.
522 --literal-pathspecs::
523 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
524 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
528 Add "glob" magic to all pathspec. This is equivalent to setting
529 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
530 globbing on individual pathspecs can be done using pathspec
534 Add "literal" magic to all pathspec. This is equivalent to setting
535 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
536 globbing on individual pathspecs can be done using pathspec
540 Add "icase" magic to all pathspec. This is equivalent to setting
541 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
546 We divide Git into high level ("porcelain") commands and low level
547 ("plumbing") commands.
549 High-level commands (porcelain)
550 -------------------------------
552 We separate the porcelain commands into the main commands and some
553 ancillary user utilities.
555 Main porcelain commands
556 ~~~~~~~~~~~~~~~~~~~~~~~
558 include::cmds-mainporcelain.txt[]
564 include::cmds-ancillarymanipulators.txt[]
568 include::cmds-ancillaryinterrogators.txt[]
571 Interacting with Others
572 ~~~~~~~~~~~~~~~~~~~~~~~
574 These commands are to interact with foreign SCM and with other
575 people via patch over e-mail.
577 include::cmds-foreignscminterface.txt[]
580 Low-level commands (plumbing)
581 -----------------------------
583 Although Git includes its
584 own porcelain layer, its low-level commands are sufficient to support
585 development of alternative porcelains. Developers of such porcelains
586 might start by reading about linkgit:git-update-index[1] and
587 linkgit:git-read-tree[1].
589 The interface (input, output, set of options and the semantics)
590 to these low-level commands are meant to be a lot more stable
591 than Porcelain level commands, because these commands are
592 primarily for scripted use. The interface to Porcelain commands
593 on the other hand are subject to change in order to improve the
596 The following description divides
597 the low-level commands into commands that manipulate objects (in
598 the repository, index, and working tree), commands that interrogate and
599 compare objects, and commands that move objects and references between
603 Manipulation commands
604 ~~~~~~~~~~~~~~~~~~~~~
606 include::cmds-plumbingmanipulators.txt[]
609 Interrogation commands
610 ~~~~~~~~~~~~~~~~~~~~~~
612 include::cmds-plumbinginterrogators.txt[]
614 In general, the interrogate commands do not touch the files in
618 Synching repositories
619 ~~~~~~~~~~~~~~~~~~~~~
621 include::cmds-synchingrepositories.txt[]
623 The following are helper commands used by the above; end users
624 typically do not use them directly.
626 include::cmds-synchelpers.txt[]
629 Internal helper commands
630 ~~~~~~~~~~~~~~~~~~~~~~~~
632 These are internal helper commands used by other commands; end
633 users typically do not use them directly.
635 include::cmds-purehelpers.txt[]
638 Configuration Mechanism
639 -----------------------
641 Git uses a simple text format to store customizations that are per
642 repository and are per user. Such a configuration file may look
647 # A '#' or ';' character indicates a comment.
652 ; Don't trust file modes
657 name = "Junio C Hamano"
658 email = "gitster@pobox.com"
662 Various commands read from the configuration file and adjust
663 their operation accordingly. See linkgit:git-config[1] for a
664 list and more details about the configuration mechanism.
667 Identifier Terminology
668 ----------------------
670 Indicates the object name for any type of object.
673 Indicates a blob object name.
676 Indicates a tree object name.
679 Indicates a commit object name.
682 Indicates a tree, commit or tag object name. A
683 command that takes a <tree-ish> argument ultimately wants to
684 operate on a <tree> object but automatically dereferences
685 <commit> and <tag> objects that point at a <tree>.
688 Indicates a commit or tag object name. A
689 command that takes a <commit-ish> argument ultimately wants to
690 operate on a <commit> object but automatically dereferences
691 <tag> objects that point at a <commit>.
694 Indicates that an object type is required.
695 Currently one of: `blob`, `tree`, `commit`, or `tag`.
698 Indicates a filename - almost always relative to the
699 root of the tree structure `GIT_INDEX_FILE` describes.
703 Any Git command accepting any <object> can also use the following
707 indicates the head of the current branch.
711 (i.e. a `refs/tags/<tag>` reference).
715 (i.e. a `refs/heads/<head>` reference).
717 For a more complete list of ways to spell object names, see
718 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
721 File/Directory Structure
722 ------------------------
724 Please see the linkgit:gitrepository-layout[5] document.
726 Read linkgit:githooks[5] for more details about each hook.
728 Higher level SCMs may provide and manage additional information in the
734 Please see linkgit:gitglossary[7].
737 Environment Variables
738 ---------------------
739 Various Git commands use the following environment variables:
743 These environment variables apply to 'all' core Git commands. Nb: it
744 is worth noting that they may be used/overridden by SCMS sitting above
745 Git so take care if using Cogito etc.
748 This environment allows the specification of an alternate
749 index file. If not specified, the default of `$GIT_DIR/index`
752 'GIT_INDEX_VERSION'::
753 This environment variable allows the specification of an index
754 version for new repositories. It won't affect existing index
755 files. By default index file version [23] is used.
757 'GIT_OBJECT_DIRECTORY'::
758 If the object storage directory is specified via this
759 environment variable then the sha1 directories are created
760 underneath - otherwise the default `$GIT_DIR/objects`
763 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
764 Due to the immutable nature of Git objects, old objects can be
765 archived into shared, read-only directories. This variable
766 specifies a ":" separated (on Windows ";" separated) list
767 of Git object directories which can be used to search for Git
768 objects. New objects will not be written to these directories.
771 If the 'GIT_DIR' environment variable is set then it
772 specifies a path to use instead of the default `.git`
773 for the base of the repository.
774 The '--git-dir' command-line option also sets this value.
777 Set the path to the root of the working tree.
778 This can also be controlled by the '--work-tree' command-line
779 option and the core.worktree configuration variable.
782 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
783 The '--namespace' command-line option also sets this value.
785 'GIT_CEILING_DIRECTORIES'::
786 This should be a colon-separated list of absolute paths. If
787 set, it is a list of directories that Git should not chdir up
788 into while looking for a repository directory (useful for
789 excluding slow-loading network directories). It will not
790 exclude the current working directory or a GIT_DIR set on the
791 command line or in the environment. Normally, Git has to read
792 the entries in this list and resolve any symlink that
793 might be present in order to compare them with the current
794 directory. However, if even this access is slow, you
795 can add an empty entry to the list to tell Git that the
796 subsequent entries are not symlinks and needn't be resolved;
798 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
800 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
801 When run in a directory that does not have ".git" repository
802 directory, Git tries to find such a directory in the parent
803 directories to find the top of the working tree, but by default it
804 does not cross filesystem boundaries. This environment variable
805 can be set to true to tell Git not to stop at filesystem
806 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
807 an explicit repository directory set via 'GIT_DIR' or on the
815 'GIT_COMMITTER_NAME'::
816 'GIT_COMMITTER_EMAIL'::
817 'GIT_COMMITTER_DATE'::
819 see linkgit:git-commit-tree[1]
824 Only valid setting is "--unified=??" or "-u??" to set the
825 number of context lines shown when a unified diff is created.
826 This takes precedence over any "-U" or "--unified" option
827 value passed on the Git diff command line.
829 'GIT_EXTERNAL_DIFF'::
830 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
831 program named by it is called, instead of the diff invocation
832 described above. For a path that is added, removed, or modified,
833 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
835 path old-file old-hex old-mode new-file new-hex new-mode
839 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
840 contents of <old|new>,
841 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
842 <old|new>-mode:: are the octal representation of the file modes.
844 The file parameters can point at the user's working file
845 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
846 when a new file is added), or a temporary file (e.g. `old-file` in the
847 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
848 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
850 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
853 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
854 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
856 'GIT_DIFF_PATH_COUNTER'::
857 A 1-based counter incremented by one for every path.
859 'GIT_DIFF_PATH_TOTAL'::
860 The total number of paths.
864 'GIT_MERGE_VERBOSITY'::
865 A number controlling the amount of output shown by
866 the recursive merge strategy. Overrides merge.verbosity.
867 See linkgit:git-merge[1]
870 This environment variable overrides `$PAGER`. If it is set
871 to an empty string or to the value "cat", Git will not launch
872 a pager. See also the `core.pager` option in
873 linkgit:git-config[1].
876 This environment variable overrides `$EDITOR` and `$VISUAL`.
877 It is used by several Git commands when, on interactive mode,
878 an editor is to be launched. See also linkgit:git-var[1]
879 and the `core.editor` option in linkgit:git-config[1].
882 If this environment variable is set then 'git fetch'
883 and 'git push' will use this command instead
884 of 'ssh' when they need to connect to a remote system.
885 The '$GIT_SSH' command will be given exactly two or
886 four arguments: the 'username@host' (or just 'host')
887 from the URL and the shell command to execute on that
888 remote system, optionally preceded by '-p' (literally) and
889 the 'port' from the URL when it specifies something other
890 than the default SSH port.
892 To pass options to the program that you want to list in GIT_SSH
893 you will need to wrap the program and options into a shell script,
894 then set GIT_SSH to refer to the shell script.
896 Usually it is easier to configure any desired options through your
897 personal `.ssh/config` file. Please consult your ssh documentation
901 If this environment variable is set, then Git commands which need to
902 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
903 will call this program with a suitable prompt as command-line argument
904 and read the password from its STDOUT. See also the 'core.askpass'
905 option in linkgit:git-config[1].
907 'GIT_CONFIG_NOSYSTEM'::
908 Whether to skip reading settings from the system-wide
909 `$(prefix)/etc/gitconfig` file. This environment variable can
910 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
911 predictable environment for a picky script, or you can set it
912 temporarily to avoid using a buggy `/etc/gitconfig` file while
913 waiting for someone with sufficient permissions to fix it.
916 If this environment variable is set to "1", then commands such
917 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
918 'git check-attr' and 'git check-ignore' will
919 force a flush of the output stream after each record have been
921 variable is set to "0", the output of these commands will be done
922 using completely buffered I/O. If this environment variable is
923 not set, Git will choose buffered or record-oriented flushing
924 based on whether stdout appears to be redirected to a file or not.
927 Enables general trace messages, e.g. alias expansion, built-in
928 command execution and external command execution.
930 If this variable is set to "1", "2" or "true" (comparison
931 is case insensitive), trace messages will be printed to
934 If the variable is set to an integer value greater than 2
935 and lower than 10 (strictly) then Git will interpret this
936 value as an open file descriptor and will try to write the
937 trace messages into this file descriptor.
939 Alternatively, if the variable is set to an absolute path
940 (starting with a '/' character), Git will interpret this
941 as a file path and will try to write the trace messages
944 Unsetting the variable, or setting it to empty, "0" or
945 "false" (case insensitive) disables trace messages.
947 'GIT_TRACE_PACK_ACCESS'::
948 Enables trace messages for all accesses to any packs. For each
949 access, the pack file name and an offset in the pack is
950 recorded. This may be helpful for troubleshooting some
951 pack-related performance problems.
952 See 'GIT_TRACE' for available trace output options.
955 Enables trace messages for all packets coming in or out of a
956 given program. This can help with debugging object negotiation
957 or other protocol issues. Tracing is turned off at a packet
958 starting with "PACK".
959 See 'GIT_TRACE' for available trace output options.
961 'GIT_TRACE_PERFORMANCE'::
962 Enables performance related trace messages, e.g. total execution
963 time of each Git command.
964 See 'GIT_TRACE' for available trace output options.
967 Enables trace messages printing the .git, working tree and current
968 working directory after Git has completed its setup phase.
969 See 'GIT_TRACE' for available trace output options.
971 'GIT_TRACE_SHALLOW'::
972 Enables trace messages that can help debugging fetching /
973 cloning of shallow repositories.
974 See 'GIT_TRACE' for available trace output options.
976 GIT_LITERAL_PATHSPECS::
977 Setting this variable to `1` will cause Git to treat all
978 pathspecs literally, rather than as glob patterns. For example,
979 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
980 for commits that touch the path `*.c`, not any paths that the
981 glob `*.c` matches. You might want this if you are feeding
982 literal paths to Git (e.g., paths previously given to you by
983 `git ls-tree`, `--raw` diff output, etc).
986 Setting this variable to `1` will cause Git to treat all
987 pathspecs as glob patterns (aka "glob" magic).
989 GIT_NOGLOB_PATHSPECS::
990 Setting this variable to `1` will cause Git to treat all
991 pathspecs as literal (aka "literal" magic).
993 GIT_ICASE_PATHSPECS::
994 Setting this variable to `1` will cause Git to treat all
995 pathspecs as case-insensitive.
997 'GIT_REFLOG_ACTION'::
998 When a ref is updated, reflog entries are created to keep
999 track of the reason why the ref was updated (which is
1000 typically the name of the high-level command that updated
1001 the ref), in addition to the old and new values of the ref.
1002 A scripted Porcelain command can use set_reflog_action
1003 helper function in `git-sh-setup` to set its name to this
1004 variable when it is invoked as the top level command by the
1005 end user, to be recorded in the body of the reflog.
1008 Discussion[[Discussion]]
1009 ------------------------
1011 More detail on the following is available from the
1012 link:user-manual.html#git-concepts[Git concepts chapter of the
1013 user-manual] and linkgit:gitcore-tutorial[7].
1015 A Git project normally consists of a working directory with a ".git"
1016 subdirectory at the top level. The .git directory contains, among other
1017 things, a compressed object database representing the complete history
1018 of the project, an "index" file which links that history to the current
1019 contents of the working tree, and named pointers into that history such
1020 as tags and branch heads.
1022 The object database contains objects of three main types: blobs, which
1023 hold file data; trees, which point to blobs and other trees to build up
1024 directory hierarchies; and commits, which each reference a single tree
1025 and some number of parent commits.
1027 The commit, equivalent to what other systems call a "changeset" or
1028 "version", represents a step in the project's history, and each parent
1029 represents an immediately preceding step. Commits with more than one
1030 parent represent merges of independent lines of development.
1032 All objects are named by the SHA-1 hash of their contents, normally
1033 written as a string of 40 hex digits. Such names are globally unique.
1034 The entire history leading up to a commit can be vouched for by signing
1035 just that commit. A fourth object type, the tag, is provided for this
1038 When first created, objects are stored in individual files, but for
1039 efficiency may later be compressed together into "pack files".
1041 Named pointers called refs mark interesting points in history. A ref
1042 may contain the SHA-1 name of an object or the name of another ref. Refs
1043 with names beginning `ref/head/` contain the SHA-1 name of the most
1044 recent commit (or "head") of a branch under development. SHA-1 names of
1045 tags of interest are stored under `ref/tags/`. A special ref named
1046 `HEAD` contains the name of the currently checked-out branch.
1048 The index file is initialized with a list of all paths and, for each
1049 path, a blob object and a set of attributes. The blob object represents
1050 the contents of the file as of the head of the current branch. The
1051 attributes (last modified time, size, etc.) are taken from the
1052 corresponding file in the working tree. Subsequent changes to the
1053 working tree can be found by comparing these attributes. The index may
1054 be updated with new content, and new commits may be created from the
1055 content stored in the index.
1057 The index is also capable of storing multiple entries (called "stages")
1058 for a given pathname. These stages are used to hold the various
1059 unmerged version of a file when a merge is in progress.
1061 FURTHER DOCUMENTATION
1062 ---------------------
1064 See the references in the "description" section to get started
1065 using Git. The following is probably more detail than necessary
1066 for a first-time user.
1068 The link:user-manual.html#git-concepts[Git concepts chapter of the
1069 user-manual] and linkgit:gitcore-tutorial[7] both provide
1070 introductions to the underlying Git architecture.
1072 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1074 See also the link:howto-index.html[howto] documents for some useful
1077 The internals are documented in the
1078 link:technical/api-index.html[Git API documentation].
1080 Users migrating from CVS may also want to
1081 read linkgit:gitcvs-migration[7].
1086 Git was started by Linus Torvalds, and is currently maintained by Junio
1087 C Hamano. Numerous contributions have come from the Git mailing list
1088 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1089 gives you a more complete list of contributors.
1091 If you have a clone of git.git itself, the
1092 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1093 the authors for specific parts of the project.
1098 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1099 development and maintenance is primarily done. You do not have to be
1100 subscribed to the list to send a message there.
1104 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1105 link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7],
1106 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1107 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1108 linkgit:gitworkflows[7]
1112 Part of the linkgit:git[1] suite