6 git - the stupid content tracker
12 'git' [--version] [--help] [-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 'master'
43 branch of the `git.git` repository.
44 Documentation for older releases are available here:
46 * link:v1.8.1.3/git.html[documentation for release 1.8.1.3]
49 link:RelNotes/1.8.1.3.txt[1.8.1.3],
50 link:RelNotes/1.8.1.2.txt[1.8.1.2],
51 link:RelNotes/1.8.1.1.txt[1.8.1.1],
52 link:RelNotes/1.8.1.txt[1.8.1].
54 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
57 link:RelNotes/1.8.0.3.txt[1.8.0.3],
58 link:RelNotes/1.8.0.2.txt[1.8.0.2],
59 link:RelNotes/1.8.0.1.txt[1.8.0.1],
60 link:RelNotes/1.8.0.txt[1.8.0].
62 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
65 link:RelNotes/1.7.12.4.txt[1.7.12.4],
66 link:RelNotes/1.7.12.3.txt[1.7.12.3],
67 link:RelNotes/1.7.12.2.txt[1.7.12.2],
68 link:RelNotes/1.7.12.1.txt[1.7.12.1],
69 link:RelNotes/1.7.12.txt[1.7.12].
71 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
74 link:RelNotes/1.7.11.7.txt[1.7.11.7],
75 link:RelNotes/1.7.11.6.txt[1.7.11.6],
76 link:RelNotes/1.7.11.5.txt[1.7.11.5],
77 link:RelNotes/1.7.11.4.txt[1.7.11.4],
78 link:RelNotes/1.7.11.3.txt[1.7.11.3],
79 link:RelNotes/1.7.11.2.txt[1.7.11.2],
80 link:RelNotes/1.7.11.1.txt[1.7.11.1],
81 link:RelNotes/1.7.11.txt[1.7.11].
83 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
86 link:RelNotes/1.7.10.5.txt[1.7.10.5],
87 link:RelNotes/1.7.10.4.txt[1.7.10.4],
88 link:RelNotes/1.7.10.3.txt[1.7.10.3],
89 link:RelNotes/1.7.10.2.txt[1.7.10.2],
90 link:RelNotes/1.7.10.1.txt[1.7.10.1],
91 link:RelNotes/1.7.10.txt[1.7.10].
93 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
96 link:RelNotes/1.7.9.7.txt[1.7.9.7],
97 link:RelNotes/1.7.9.6.txt[1.7.9.6],
98 link:RelNotes/1.7.9.5.txt[1.7.9.5],
99 link:RelNotes/1.7.9.4.txt[1.7.9.4],
100 link:RelNotes/1.7.9.3.txt[1.7.9.3],
101 link:RelNotes/1.7.9.2.txt[1.7.9.2],
102 link:RelNotes/1.7.9.1.txt[1.7.9.1],
103 link:RelNotes/1.7.9.txt[1.7.9].
105 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
108 link:RelNotes/1.7.8.6.txt[1.7.8.6],
109 link:RelNotes/1.7.8.5.txt[1.7.8.5],
110 link:RelNotes/1.7.8.4.txt[1.7.8.4],
111 link:RelNotes/1.7.8.3.txt[1.7.8.3],
112 link:RelNotes/1.7.8.2.txt[1.7.8.2],
113 link:RelNotes/1.7.8.1.txt[1.7.8.1],
114 link:RelNotes/1.7.8.txt[1.7.8].
116 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
119 link:RelNotes/1.7.7.7.txt[1.7.7.7],
120 link:RelNotes/1.7.7.6.txt[1.7.7.6],
121 link:RelNotes/1.7.7.5.txt[1.7.7.5],
122 link:RelNotes/1.7.7.4.txt[1.7.7.4],
123 link:RelNotes/1.7.7.3.txt[1.7.7.3],
124 link:RelNotes/1.7.7.2.txt[1.7.7.2],
125 link:RelNotes/1.7.7.1.txt[1.7.7.1],
126 link:RelNotes/1.7.7.txt[1.7.7].
128 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
131 link:RelNotes/1.7.6.6.txt[1.7.6.6],
132 link:RelNotes/1.7.6.5.txt[1.7.6.5],
133 link:RelNotes/1.7.6.4.txt[1.7.6.4],
134 link:RelNotes/1.7.6.3.txt[1.7.6.3],
135 link:RelNotes/1.7.6.2.txt[1.7.6.2],
136 link:RelNotes/1.7.6.1.txt[1.7.6.1],
137 link:RelNotes/1.7.6.txt[1.7.6].
139 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
142 link:RelNotes/1.7.5.4.txt[1.7.5.4],
143 link:RelNotes/1.7.5.3.txt[1.7.5.3],
144 link:RelNotes/1.7.5.2.txt[1.7.5.2],
145 link:RelNotes/1.7.5.1.txt[1.7.5.1],
146 link:RelNotes/1.7.5.txt[1.7.5].
148 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
151 link:RelNotes/1.7.4.5.txt[1.7.4.5],
152 link:RelNotes/1.7.4.4.txt[1.7.4.4],
153 link:RelNotes/1.7.4.3.txt[1.7.4.3],
154 link:RelNotes/1.7.4.2.txt[1.7.4.2],
155 link:RelNotes/1.7.4.1.txt[1.7.4.1],
156 link:RelNotes/1.7.4.txt[1.7.4].
158 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
161 link:RelNotes/1.7.3.5.txt[1.7.3.5],
162 link:RelNotes/1.7.3.4.txt[1.7.3.4],
163 link:RelNotes/1.7.3.3.txt[1.7.3.3],
164 link:RelNotes/1.7.3.2.txt[1.7.3.2],
165 link:RelNotes/1.7.3.1.txt[1.7.3.1],
166 link:RelNotes/1.7.3.txt[1.7.3].
168 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
171 link:RelNotes/1.7.2.5.txt[1.7.2.5],
172 link:RelNotes/1.7.2.4.txt[1.7.2.4],
173 link:RelNotes/1.7.2.3.txt[1.7.2.3],
174 link:RelNotes/1.7.2.2.txt[1.7.2.2],
175 link:RelNotes/1.7.2.1.txt[1.7.2.1],
176 link:RelNotes/1.7.2.txt[1.7.2].
178 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
181 link:RelNotes/1.7.1.4.txt[1.7.1.4],
182 link:RelNotes/1.7.1.3.txt[1.7.1.3],
183 link:RelNotes/1.7.1.2.txt[1.7.1.2],
184 link:RelNotes/1.7.1.1.txt[1.7.1.1],
185 link:RelNotes/1.7.1.txt[1.7.1].
187 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
190 link:RelNotes/1.7.0.9.txt[1.7.0.9],
191 link:RelNotes/1.7.0.8.txt[1.7.0.8],
192 link:RelNotes/1.7.0.7.txt[1.7.0.7],
193 link:RelNotes/1.7.0.6.txt[1.7.0.6],
194 link:RelNotes/1.7.0.5.txt[1.7.0.5],
195 link:RelNotes/1.7.0.4.txt[1.7.0.4],
196 link:RelNotes/1.7.0.3.txt[1.7.0.3],
197 link:RelNotes/1.7.0.2.txt[1.7.0.2],
198 link:RelNotes/1.7.0.1.txt[1.7.0.1],
199 link:RelNotes/1.7.0.txt[1.7.0].
201 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
204 link:RelNotes/1.6.6.3.txt[1.6.6.3],
205 link:RelNotes/1.6.6.2.txt[1.6.6.2],
206 link:RelNotes/1.6.6.1.txt[1.6.6.1],
207 link:RelNotes/1.6.6.txt[1.6.6].
209 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
212 link:RelNotes/1.6.5.9.txt[1.6.5.9],
213 link:RelNotes/1.6.5.8.txt[1.6.5.8],
214 link:RelNotes/1.6.5.7.txt[1.6.5.7],
215 link:RelNotes/1.6.5.6.txt[1.6.5.6],
216 link:RelNotes/1.6.5.5.txt[1.6.5.5],
217 link:RelNotes/1.6.5.4.txt[1.6.5.4],
218 link:RelNotes/1.6.5.3.txt[1.6.5.3],
219 link:RelNotes/1.6.5.2.txt[1.6.5.2],
220 link:RelNotes/1.6.5.1.txt[1.6.5.1],
221 link:RelNotes/1.6.5.txt[1.6.5].
223 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
226 link:RelNotes/1.6.4.5.txt[1.6.4.5],
227 link:RelNotes/1.6.4.4.txt[1.6.4.4],
228 link:RelNotes/1.6.4.3.txt[1.6.4.3],
229 link:RelNotes/1.6.4.2.txt[1.6.4.2],
230 link:RelNotes/1.6.4.1.txt[1.6.4.1],
231 link:RelNotes/1.6.4.txt[1.6.4].
233 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
236 link:RelNotes/1.6.3.4.txt[1.6.3.4],
237 link:RelNotes/1.6.3.3.txt[1.6.3.3],
238 link:RelNotes/1.6.3.2.txt[1.6.3.2],
239 link:RelNotes/1.6.3.1.txt[1.6.3.1],
240 link:RelNotes/1.6.3.txt[1.6.3].
243 link:RelNotes/1.6.2.5.txt[1.6.2.5],
244 link:RelNotes/1.6.2.4.txt[1.6.2.4],
245 link:RelNotes/1.6.2.3.txt[1.6.2.3],
246 link:RelNotes/1.6.2.2.txt[1.6.2.2],
247 link:RelNotes/1.6.2.1.txt[1.6.2.1],
248 link:RelNotes/1.6.2.txt[1.6.2].
250 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
253 link:RelNotes/1.6.1.3.txt[1.6.1.3],
254 link:RelNotes/1.6.1.2.txt[1.6.1.2],
255 link:RelNotes/1.6.1.1.txt[1.6.1.1],
256 link:RelNotes/1.6.1.txt[1.6.1].
258 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
261 link:RelNotes/1.6.0.6.txt[1.6.0.6],
262 link:RelNotes/1.6.0.5.txt[1.6.0.5],
263 link:RelNotes/1.6.0.4.txt[1.6.0.4],
264 link:RelNotes/1.6.0.3.txt[1.6.0.3],
265 link:RelNotes/1.6.0.2.txt[1.6.0.2],
266 link:RelNotes/1.6.0.1.txt[1.6.0.1],
267 link:RelNotes/1.6.0.txt[1.6.0].
269 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
272 link:RelNotes/1.5.6.6.txt[1.5.6.6],
273 link:RelNotes/1.5.6.5.txt[1.5.6.5],
274 link:RelNotes/1.5.6.4.txt[1.5.6.4],
275 link:RelNotes/1.5.6.3.txt[1.5.6.3],
276 link:RelNotes/1.5.6.2.txt[1.5.6.2],
277 link:RelNotes/1.5.6.1.txt[1.5.6.1],
278 link:RelNotes/1.5.6.txt[1.5.6].
280 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
283 link:RelNotes/1.5.5.6.txt[1.5.5.6],
284 link:RelNotes/1.5.5.5.txt[1.5.5.5],
285 link:RelNotes/1.5.5.4.txt[1.5.5.4],
286 link:RelNotes/1.5.5.3.txt[1.5.5.3],
287 link:RelNotes/1.5.5.2.txt[1.5.5.2],
288 link:RelNotes/1.5.5.1.txt[1.5.5.1],
289 link:RelNotes/1.5.5.txt[1.5.5].
291 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
294 link:RelNotes/1.5.4.7.txt[1.5.4.7],
295 link:RelNotes/1.5.4.6.txt[1.5.4.6],
296 link:RelNotes/1.5.4.5.txt[1.5.4.5],
297 link:RelNotes/1.5.4.4.txt[1.5.4.4],
298 link:RelNotes/1.5.4.3.txt[1.5.4.3],
299 link:RelNotes/1.5.4.2.txt[1.5.4.2],
300 link:RelNotes/1.5.4.1.txt[1.5.4.1],
301 link:RelNotes/1.5.4.txt[1.5.4].
303 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
306 link:RelNotes/1.5.3.8.txt[1.5.3.8],
307 link:RelNotes/1.5.3.7.txt[1.5.3.7],
308 link:RelNotes/1.5.3.6.txt[1.5.3.6],
309 link:RelNotes/1.5.3.5.txt[1.5.3.5],
310 link:RelNotes/1.5.3.4.txt[1.5.3.4],
311 link:RelNotes/1.5.3.3.txt[1.5.3.3],
312 link:RelNotes/1.5.3.2.txt[1.5.3.2],
313 link:RelNotes/1.5.3.1.txt[1.5.3.1],
314 link:RelNotes/1.5.3.txt[1.5.3].
316 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
319 link:RelNotes/1.5.2.5.txt[1.5.2.5],
320 link:RelNotes/1.5.2.4.txt[1.5.2.4],
321 link:RelNotes/1.5.2.3.txt[1.5.2.3],
322 link:RelNotes/1.5.2.2.txt[1.5.2.2],
323 link:RelNotes/1.5.2.1.txt[1.5.2.1],
324 link:RelNotes/1.5.2.txt[1.5.2].
326 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
329 link:RelNotes/1.5.1.6.txt[1.5.1.6],
330 link:RelNotes/1.5.1.5.txt[1.5.1.5],
331 link:RelNotes/1.5.1.4.txt[1.5.1.4],
332 link:RelNotes/1.5.1.3.txt[1.5.1.3],
333 link:RelNotes/1.5.1.2.txt[1.5.1.2],
334 link:RelNotes/1.5.1.1.txt[1.5.1.1],
335 link:RelNotes/1.5.1.txt[1.5.1].
337 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
340 link:RelNotes/1.5.0.7.txt[1.5.0.7],
341 link:RelNotes/1.5.0.6.txt[1.5.0.6],
342 link:RelNotes/1.5.0.5.txt[1.5.0.5],
343 link:RelNotes/1.5.0.3.txt[1.5.0.3],
344 link:RelNotes/1.5.0.2.txt[1.5.0.2],
345 link:RelNotes/1.5.0.1.txt[1.5.0.1],
346 link:RelNotes/1.5.0.txt[1.5.0].
348 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
349 link:v1.3.3/git.html[1.3.3],
350 link:v1.2.6/git.html[1.2.6],
351 link:v1.0.13/git.html[1.0.13].
360 Prints the git suite version that the 'git' program came from.
363 Prints the synopsis and a list of the most commonly used
364 commands. If the option '--all' or '-a' is given then all
365 available commands are printed. If a git command is named this
366 option will bring up the manual page for that command.
368 Other options are available to control how the manual page is
369 displayed. See linkgit:git-help[1] for more information,
370 because `git --help ...` is converted internally into `git
374 Pass a configuration parameter to the command. The value
375 given will override values from configuration files.
376 The <name> is expected in the same format as listed by
377 'git config' (subkeys separated by dots).
379 --exec-path[=<path>]::
380 Path to wherever your core git programs are installed.
381 This can also be controlled by setting the GIT_EXEC_PATH
382 environment variable. If no path is given, 'git' will print
383 the current setting and then exit.
386 Print the path, without trailing slash, where git's HTML
387 documentation is installed and exit.
390 Print the manpath (see `man(1)`) for the man pages for
391 this version of git and exit.
394 Print the path where the Info files documenting this
395 version of git are installed and exit.
399 Pipe all output into 'less' (or if set, $PAGER) if standard
400 output is a terminal. This overrides the `pager.<cmd>`
401 configuration options (see the "Configuration Mechanism" section
405 Do not pipe git output into a pager.
408 Set the path to the repository. This can also be controlled by
409 setting the GIT_DIR environment variable. It can be an absolute
410 path or relative path to current working directory.
413 Set the path to the working tree. It can be an absolute path
414 or a path relative to the current working directory.
415 This can also be controlled by setting the GIT_WORK_TREE
416 environment variable and the core.worktree configuration
417 variable (see core.worktree in linkgit:git-config[1] for a
418 more detailed discussion).
421 Set the git namespace. See linkgit:gitnamespaces[7] for more
422 details. Equivalent to setting the `GIT_NAMESPACE` environment
426 Treat the repository as a bare repository. If GIT_DIR
427 environment is not set, it is set to the current working
430 --no-replace-objects::
431 Do not use replacement refs to replace git objects. See
432 linkgit:git-replace[1] for more information.
438 We divide git into high level ("porcelain") commands and low level
439 ("plumbing") commands.
441 High-level commands (porcelain)
442 -------------------------------
444 We separate the porcelain commands into the main commands and some
445 ancillary user utilities.
447 Main porcelain commands
448 ~~~~~~~~~~~~~~~~~~~~~~~
450 include::cmds-mainporcelain.txt[]
456 include::cmds-ancillarymanipulators.txt[]
460 include::cmds-ancillaryinterrogators.txt[]
463 Interacting with Others
464 ~~~~~~~~~~~~~~~~~~~~~~~
466 These commands are to interact with foreign SCM and with other
467 people via patch over e-mail.
469 include::cmds-foreignscminterface.txt[]
472 Low-level commands (plumbing)
473 -----------------------------
475 Although git includes its
476 own porcelain layer, its low-level commands are sufficient to support
477 development of alternative porcelains. Developers of such porcelains
478 might start by reading about linkgit:git-update-index[1] and
479 linkgit:git-read-tree[1].
481 The interface (input, output, set of options and the semantics)
482 to these low-level commands are meant to be a lot more stable
483 than Porcelain level commands, because these commands are
484 primarily for scripted use. The interface to Porcelain commands
485 on the other hand are subject to change in order to improve the
488 The following description divides
489 the low-level commands into commands that manipulate objects (in
490 the repository, index, and working tree), commands that interrogate and
491 compare objects, and commands that move objects and references between
495 Manipulation commands
496 ~~~~~~~~~~~~~~~~~~~~~
498 include::cmds-plumbingmanipulators.txt[]
501 Interrogation commands
502 ~~~~~~~~~~~~~~~~~~~~~~
504 include::cmds-plumbinginterrogators.txt[]
506 In general, the interrogate commands do not touch the files in
510 Synching repositories
511 ~~~~~~~~~~~~~~~~~~~~~
513 include::cmds-synchingrepositories.txt[]
515 The following are helper commands used by the above; end users
516 typically do not use them directly.
518 include::cmds-synchelpers.txt[]
521 Internal helper commands
522 ~~~~~~~~~~~~~~~~~~~~~~~~
524 These are internal helper commands used by other commands; end
525 users typically do not use them directly.
527 include::cmds-purehelpers.txt[]
530 Configuration Mechanism
531 -----------------------
533 Git uses a simple text format to store customizations that are per
534 repository and are per user. Such a configuration file may look
539 # A '#' or ';' character indicates a comment.
544 ; Don't trust file modes
549 name = "Junio C Hamano"
550 email = "gitster@pobox.com"
554 Various commands read from the configuration file and adjust
555 their operation accordingly. See linkgit:git-config[1] for a
556 list and more details about the configuration mechanism.
559 Identifier Terminology
560 ----------------------
562 Indicates the object name for any type of object.
565 Indicates a blob object name.
568 Indicates a tree object name.
571 Indicates a commit object name.
574 Indicates a tree, commit or tag object name. A
575 command that takes a <tree-ish> argument ultimately wants to
576 operate on a <tree> object but automatically dereferences
577 <commit> and <tag> objects that point at a <tree>.
580 Indicates a commit or tag object name. A
581 command that takes a <commit-ish> argument ultimately wants to
582 operate on a <commit> object but automatically dereferences
583 <tag> objects that point at a <commit>.
586 Indicates that an object type is required.
587 Currently one of: `blob`, `tree`, `commit`, or `tag`.
590 Indicates a filename - almost always relative to the
591 root of the tree structure `GIT_INDEX_FILE` describes.
595 Any git command accepting any <object> can also use the following
599 indicates the head of the current branch.
603 (i.e. a `refs/tags/<tag>` reference).
607 (i.e. a `refs/heads/<head>` reference).
609 For a more complete list of ways to spell object names, see
610 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
613 File/Directory Structure
614 ------------------------
616 Please see the linkgit:gitrepository-layout[5] document.
618 Read linkgit:githooks[5] for more details about each hook.
620 Higher level SCMs may provide and manage additional information in the
626 Please see linkgit:gitglossary[7].
629 Environment Variables
630 ---------------------
631 Various git commands use the following environment variables:
635 These environment variables apply to 'all' core git commands. Nb: it
636 is worth noting that they may be used/overridden by SCMS sitting above
637 git so take care if using Cogito etc.
640 This environment allows the specification of an alternate
641 index file. If not specified, the default of `$GIT_DIR/index`
644 'GIT_OBJECT_DIRECTORY'::
645 If the object storage directory is specified via this
646 environment variable then the sha1 directories are created
647 underneath - otherwise the default `$GIT_DIR/objects`
650 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
651 Due to the immutable nature of git objects, old objects can be
652 archived into shared, read-only directories. This variable
653 specifies a ":" separated (on Windows ";" separated) list
654 of git object directories which can be used to search for git
655 objects. New objects will not be written to these directories.
658 If the 'GIT_DIR' environment variable is set then it
659 specifies a path to use instead of the default `.git`
660 for the base of the repository.
661 The '--git-dir' command-line option also sets this value.
664 Set the path to the working tree. The value will not be
665 used in combination with repositories found automatically in
666 a .git directory (i.e. $GIT_DIR is not set).
667 This can also be controlled by the '--work-tree' command line
668 option and the core.worktree configuration variable.
671 Set the git namespace; see linkgit:gitnamespaces[7] for details.
672 The '--namespace' command-line option also sets this value.
674 'GIT_CEILING_DIRECTORIES'::
675 This should be a colon-separated list of absolute paths.
676 If set, it is a list of directories that git should not chdir
677 up into while looking for a repository directory.
678 It will not exclude the current working directory or
679 a GIT_DIR set on the command line or in the environment.
680 (Useful for excluding slow-loading network directories.)
682 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
683 When run in a directory that does not have ".git" repository
684 directory, git tries to find such a directory in the parent
685 directories to find the top of the working tree, but by default it
686 does not cross filesystem boundaries. This environment variable
687 can be set to true to tell git not to stop at filesystem
688 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
689 an explicit repository directory set via 'GIT_DIR' or on the
697 'GIT_COMMITTER_NAME'::
698 'GIT_COMMITTER_EMAIL'::
699 'GIT_COMMITTER_DATE'::
701 see linkgit:git-commit-tree[1]
706 Only valid setting is "--unified=??" or "-u??" to set the
707 number of context lines shown when a unified diff is created.
708 This takes precedence over any "-U" or "--unified" option
709 value passed on the git diff command line.
711 'GIT_EXTERNAL_DIFF'::
712 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
713 program named by it is called, instead of the diff invocation
714 described above. For a path that is added, removed, or modified,
715 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
717 path old-file old-hex old-mode new-file new-hex new-mode
721 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
722 contents of <old|new>,
723 <old|new>-hex:: are the 40-hexdigit SHA1 hashes,
724 <old|new>-mode:: are the octal representation of the file modes.
726 The file parameters can point at the user's working file
727 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
728 when a new file is added), or a temporary file (e.g. `old-file` in the
729 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
730 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
732 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
737 'GIT_MERGE_VERBOSITY'::
738 A number controlling the amount of output shown by
739 the recursive merge strategy. Overrides merge.verbosity.
740 See linkgit:git-merge[1]
743 This environment variable overrides `$PAGER`. If it is set
744 to an empty string or to the value "cat", git will not launch
745 a pager. See also the `core.pager` option in
746 linkgit:git-config[1].
749 This environment variable overrides `$EDITOR` and `$VISUAL`.
750 It is used by several git commands when, on interactive mode,
751 an editor is to be launched. See also linkgit:git-var[1]
752 and the `core.editor` option in linkgit:git-config[1].
755 If this environment variable is set then 'git fetch'
756 and 'git push' will use this command instead
757 of 'ssh' when they need to connect to a remote system.
758 The '$GIT_SSH' command will be given exactly two arguments:
759 the 'username@host' (or just 'host') from the URL and the
760 shell command to execute on that remote system.
762 To pass options to the program that you want to list in GIT_SSH
763 you will need to wrap the program and options into a shell script,
764 then set GIT_SSH to refer to the shell script.
766 Usually it is easier to configure any desired options through your
767 personal `.ssh/config` file. Please consult your ssh documentation
771 If this environment variable is set, then git commands which need to
772 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
773 will call this program with a suitable prompt as command line argument
774 and read the password from its STDOUT. See also the 'core.askpass'
775 option in linkgit:git-config[1].
777 'GIT_CONFIG_NOSYSTEM'::
778 Whether to skip reading settings from the system-wide
779 `$(prefix)/etc/gitconfig` file. This environment variable can
780 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
781 predictable environment for a picky script, or you can set it
782 temporarily to avoid using a buggy `/etc/gitconfig` file while
783 waiting for someone with sufficient permissions to fix it.
786 If this environment variable is set to "1", then commands such
787 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
788 and 'git whatchanged' will force a flush of the output stream
789 after each commit-oriented record have been flushed. If this
790 variable is set to "0", the output of these commands will be done
791 using completely buffered I/O. If this environment variable is
792 not set, git will choose buffered or record-oriented flushing
793 based on whether stdout appears to be redirected to a file or not.
796 If this variable is set to "1", "2" or "true" (comparison
797 is case insensitive), git will print `trace:` messages on
798 stderr telling about alias expansion, built-in command
799 execution and external command execution.
800 If this variable is set to an integer value greater than 1
801 and lower than 10 (strictly) then git will interpret this
802 value as an open file descriptor and will try to write the
803 trace messages into this file descriptor.
804 Alternatively, if this variable is set to an absolute path
805 (starting with a '/' character), git will interpret this
806 as a file path and will try to write the trace messages
809 Discussion[[Discussion]]
810 ------------------------
812 More detail on the following is available from the
813 link:user-manual.html#git-concepts[git concepts chapter of the
814 user-manual] and linkgit:gitcore-tutorial[7].
816 A git project normally consists of a working directory with a ".git"
817 subdirectory at the top level. The .git directory contains, among other
818 things, a compressed object database representing the complete history
819 of the project, an "index" file which links that history to the current
820 contents of the working tree, and named pointers into that history such
821 as tags and branch heads.
823 The object database contains objects of three main types: blobs, which
824 hold file data; trees, which point to blobs and other trees to build up
825 directory hierarchies; and commits, which each reference a single tree
826 and some number of parent commits.
828 The commit, equivalent to what other systems call a "changeset" or
829 "version", represents a step in the project's history, and each parent
830 represents an immediately preceding step. Commits with more than one
831 parent represent merges of independent lines of development.
833 All objects are named by the SHA1 hash of their contents, normally
834 written as a string of 40 hex digits. Such names are globally unique.
835 The entire history leading up to a commit can be vouched for by signing
836 just that commit. A fourth object type, the tag, is provided for this
839 When first created, objects are stored in individual files, but for
840 efficiency may later be compressed together into "pack files".
842 Named pointers called refs mark interesting points in history. A ref
843 may contain the SHA1 name of an object or the name of another ref. Refs
844 with names beginning `ref/head/` contain the SHA1 name of the most
845 recent commit (or "head") of a branch under development. SHA1 names of
846 tags of interest are stored under `ref/tags/`. A special ref named
847 `HEAD` contains the name of the currently checked-out branch.
849 The index file is initialized with a list of all paths and, for each
850 path, a blob object and a set of attributes. The blob object represents
851 the contents of the file as of the head of the current branch. The
852 attributes (last modified time, size, etc.) are taken from the
853 corresponding file in the working tree. Subsequent changes to the
854 working tree can be found by comparing these attributes. The index may
855 be updated with new content, and new commits may be created from the
856 content stored in the index.
858 The index is also capable of storing multiple entries (called "stages")
859 for a given pathname. These stages are used to hold the various
860 unmerged version of a file when a merge is in progress.
862 FURTHER DOCUMENTATION
863 ---------------------
865 See the references in the "description" section to get started
866 using git. The following is probably more detail than necessary
867 for a first-time user.
869 The link:user-manual.html#git-concepts[git concepts chapter of the
870 user-manual] and linkgit:gitcore-tutorial[7] both provide
871 introductions to the underlying git architecture.
873 See linkgit:gitworkflows[7] for an overview of recommended workflows.
875 See also the link:howto-index.html[howto] documents for some useful
878 The internals are documented in the
879 link:technical/api-index.html[GIT API documentation].
881 Users migrating from CVS may also want to
882 read linkgit:gitcvs-migration[7].
887 Git was started by Linus Torvalds, and is currently maintained by Junio
888 C Hamano. Numerous contributions have come from the git mailing list
889 <git@vger.kernel.org>. http://www.ohloh.net/p/git/contributors/summary
890 gives you a more complete list of contributors.
892 If you have a clone of git.git itself, the
893 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
894 the authors for specific parts of the project.
899 Report bugs to the Git mailing list <git@vger.kernel.org> where the
900 development and maintenance is primarily done. You do not have to be
901 subscribed to the list to send a message there.
905 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
906 link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7],
907 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
908 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
909 linkgit:gitworkflows[7]
913 Part of the linkgit:git[1] suite