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 commands, and
26 "man git-commandname" for documentation of each command. CVS users may
27 also want to read linkgit:gitcvs-migration[7]. See
28 the link:user-manual.html[Git User's Manual] for a more in-depth
31 The '<command>' is either a name of a Git command (see below) or an alias
32 as defined in the configuration file (see linkgit:git-config[1]).
34 Formatted and hyperlinked version of the latest git
35 documentation can be viewed at
36 `http://www.kernel.org/pub/software/scm/git/docs/`.
42 You are reading the documentation for the latest (possibly
43 unreleased) version of git, that is available from 'master'
44 branch of the `git.git` repository.
45 Documentation for older releases are available here:
47 * link:v1.7.11.3/git.html[documentation for release 1.7.11.3]
50 link:RelNotes/1.7.11.3.txt[1.7.11.3],
51 link:RelNotes/1.7.11.2.txt[1.7.11.2],
52 link:RelNotes/1.7.11.1.txt[1.7.11.1],
53 link:RelNotes/1.7.11.txt[1.7.11].
55 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
58 link:RelNotes/1.7.10.5.txt[1.7.10.5],
59 link:RelNotes/1.7.10.4.txt[1.7.10.4],
60 link:RelNotes/1.7.10.3.txt[1.7.10.3],
61 link:RelNotes/1.7.10.2.txt[1.7.10.2],
62 link:RelNotes/1.7.10.1.txt[1.7.10.1],
63 link:RelNotes/1.7.10.txt[1.7.10].
65 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
68 link:RelNotes/1.7.9.7.txt[1.7.9.7],
69 link:RelNotes/1.7.9.6.txt[1.7.9.6],
70 link:RelNotes/1.7.9.5.txt[1.7.9.5],
71 link:RelNotes/1.7.9.4.txt[1.7.9.4],
72 link:RelNotes/1.7.9.3.txt[1.7.9.3],
73 link:RelNotes/1.7.9.2.txt[1.7.9.2],
74 link:RelNotes/1.7.9.1.txt[1.7.9.1],
75 link:RelNotes/1.7.9.txt[1.7.9].
77 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
80 link:RelNotes/1.7.8.6.txt[1.7.8.6],
81 link:RelNotes/1.7.8.5.txt[1.7.8.5],
82 link:RelNotes/1.7.8.4.txt[1.7.8.4],
83 link:RelNotes/1.7.8.3.txt[1.7.8.3],
84 link:RelNotes/1.7.8.2.txt[1.7.8.2],
85 link:RelNotes/1.7.8.1.txt[1.7.8.1],
86 link:RelNotes/1.7.8.txt[1.7.8].
88 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
91 link:RelNotes/1.7.7.7.txt[1.7.7.7],
92 link:RelNotes/1.7.7.6.txt[1.7.7.6],
93 link:RelNotes/1.7.7.5.txt[1.7.7.5],
94 link:RelNotes/1.7.7.4.txt[1.7.7.4],
95 link:RelNotes/1.7.7.3.txt[1.7.7.3],
96 link:RelNotes/1.7.7.2.txt[1.7.7.2],
97 link:RelNotes/1.7.7.1.txt[1.7.7.1],
98 link:RelNotes/1.7.7.txt[1.7.7].
100 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
103 link:RelNotes/1.7.6.6.txt[1.7.6.6],
104 link:RelNotes/1.7.6.5.txt[1.7.6.5],
105 link:RelNotes/1.7.6.4.txt[1.7.6.4],
106 link:RelNotes/1.7.6.3.txt[1.7.6.3],
107 link:RelNotes/1.7.6.2.txt[1.7.6.2],
108 link:RelNotes/1.7.6.1.txt[1.7.6.1],
109 link:RelNotes/1.7.6.txt[1.7.6].
111 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
114 link:RelNotes/1.7.5.4.txt[1.7.5.4],
115 link:RelNotes/1.7.5.3.txt[1.7.5.3],
116 link:RelNotes/1.7.5.2.txt[1.7.5.2],
117 link:RelNotes/1.7.5.1.txt[1.7.5.1],
118 link:RelNotes/1.7.5.txt[1.7.5].
120 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
123 link:RelNotes/1.7.4.5.txt[1.7.4.5],
124 link:RelNotes/1.7.4.4.txt[1.7.4.4],
125 link:RelNotes/1.7.4.3.txt[1.7.4.3],
126 link:RelNotes/1.7.4.2.txt[1.7.4.2],
127 link:RelNotes/1.7.4.1.txt[1.7.4.1],
128 link:RelNotes/1.7.4.txt[1.7.4].
130 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
133 link:RelNotes/1.7.3.5.txt[1.7.3.5],
134 link:RelNotes/1.7.3.4.txt[1.7.3.4],
135 link:RelNotes/1.7.3.3.txt[1.7.3.3],
136 link:RelNotes/1.7.3.2.txt[1.7.3.2],
137 link:RelNotes/1.7.3.1.txt[1.7.3.1],
138 link:RelNotes/1.7.3.txt[1.7.3].
140 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
143 link:RelNotes/1.7.2.5.txt[1.7.2.5],
144 link:RelNotes/1.7.2.4.txt[1.7.2.4],
145 link:RelNotes/1.7.2.3.txt[1.7.2.3],
146 link:RelNotes/1.7.2.2.txt[1.7.2.2],
147 link:RelNotes/1.7.2.1.txt[1.7.2.1],
148 link:RelNotes/1.7.2.txt[1.7.2].
150 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
153 link:RelNotes/1.7.1.4.txt[1.7.1.4],
154 link:RelNotes/1.7.1.3.txt[1.7.1.3],
155 link:RelNotes/1.7.1.2.txt[1.7.1.2],
156 link:RelNotes/1.7.1.1.txt[1.7.1.1],
157 link:RelNotes/1.7.1.txt[1.7.1].
159 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
162 link:RelNotes/1.7.0.9.txt[1.7.0.9],
163 link:RelNotes/1.7.0.8.txt[1.7.0.8],
164 link:RelNotes/1.7.0.7.txt[1.7.0.7],
165 link:RelNotes/1.7.0.6.txt[1.7.0.6],
166 link:RelNotes/1.7.0.5.txt[1.7.0.5],
167 link:RelNotes/1.7.0.4.txt[1.7.0.4],
168 link:RelNotes/1.7.0.3.txt[1.7.0.3],
169 link:RelNotes/1.7.0.2.txt[1.7.0.2],
170 link:RelNotes/1.7.0.1.txt[1.7.0.1],
171 link:RelNotes/1.7.0.txt[1.7.0].
173 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
176 link:RelNotes/1.6.6.3.txt[1.6.6.3],
177 link:RelNotes/1.6.6.2.txt[1.6.6.2],
178 link:RelNotes/1.6.6.1.txt[1.6.6.1],
179 link:RelNotes/1.6.6.txt[1.6.6].
181 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
184 link:RelNotes/1.6.5.9.txt[1.6.5.9],
185 link:RelNotes/1.6.5.8.txt[1.6.5.8],
186 link:RelNotes/1.6.5.7.txt[1.6.5.7],
187 link:RelNotes/1.6.5.6.txt[1.6.5.6],
188 link:RelNotes/1.6.5.5.txt[1.6.5.5],
189 link:RelNotes/1.6.5.4.txt[1.6.5.4],
190 link:RelNotes/1.6.5.3.txt[1.6.5.3],
191 link:RelNotes/1.6.5.2.txt[1.6.5.2],
192 link:RelNotes/1.6.5.1.txt[1.6.5.1],
193 link:RelNotes/1.6.5.txt[1.6.5].
195 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
198 link:RelNotes/1.6.4.5.txt[1.6.4.5],
199 link:RelNotes/1.6.4.4.txt[1.6.4.4],
200 link:RelNotes/1.6.4.3.txt[1.6.4.3],
201 link:RelNotes/1.6.4.2.txt[1.6.4.2],
202 link:RelNotes/1.6.4.1.txt[1.6.4.1],
203 link:RelNotes/1.6.4.txt[1.6.4].
205 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
208 link:RelNotes/1.6.3.4.txt[1.6.3.4],
209 link:RelNotes/1.6.3.3.txt[1.6.3.3],
210 link:RelNotes/1.6.3.2.txt[1.6.3.2],
211 link:RelNotes/1.6.3.1.txt[1.6.3.1],
212 link:RelNotes/1.6.3.txt[1.6.3].
215 link:RelNotes/1.6.2.5.txt[1.6.2.5],
216 link:RelNotes/1.6.2.4.txt[1.6.2.4],
217 link:RelNotes/1.6.2.3.txt[1.6.2.3],
218 link:RelNotes/1.6.2.2.txt[1.6.2.2],
219 link:RelNotes/1.6.2.1.txt[1.6.2.1],
220 link:RelNotes/1.6.2.txt[1.6.2].
222 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
225 link:RelNotes/1.6.1.3.txt[1.6.1.3],
226 link:RelNotes/1.6.1.2.txt[1.6.1.2],
227 link:RelNotes/1.6.1.1.txt[1.6.1.1],
228 link:RelNotes/1.6.1.txt[1.6.1].
230 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
233 link:RelNotes/1.6.0.6.txt[1.6.0.6],
234 link:RelNotes/1.6.0.5.txt[1.6.0.5],
235 link:RelNotes/1.6.0.4.txt[1.6.0.4],
236 link:RelNotes/1.6.0.3.txt[1.6.0.3],
237 link:RelNotes/1.6.0.2.txt[1.6.0.2],
238 link:RelNotes/1.6.0.1.txt[1.6.0.1],
239 link:RelNotes/1.6.0.txt[1.6.0].
241 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
244 link:RelNotes/1.5.6.6.txt[1.5.6.6],
245 link:RelNotes/1.5.6.5.txt[1.5.6.5],
246 link:RelNotes/1.5.6.4.txt[1.5.6.4],
247 link:RelNotes/1.5.6.3.txt[1.5.6.3],
248 link:RelNotes/1.5.6.2.txt[1.5.6.2],
249 link:RelNotes/1.5.6.1.txt[1.5.6.1],
250 link:RelNotes/1.5.6.txt[1.5.6].
252 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
255 link:RelNotes/1.5.5.6.txt[1.5.5.6],
256 link:RelNotes/1.5.5.5.txt[1.5.5.5],
257 link:RelNotes/1.5.5.4.txt[1.5.5.4],
258 link:RelNotes/1.5.5.3.txt[1.5.5.3],
259 link:RelNotes/1.5.5.2.txt[1.5.5.2],
260 link:RelNotes/1.5.5.1.txt[1.5.5.1],
261 link:RelNotes/1.5.5.txt[1.5.5].
263 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
266 link:RelNotes/1.5.4.7.txt[1.5.4.7],
267 link:RelNotes/1.5.4.6.txt[1.5.4.6],
268 link:RelNotes/1.5.4.5.txt[1.5.4.5],
269 link:RelNotes/1.5.4.4.txt[1.5.4.4],
270 link:RelNotes/1.5.4.3.txt[1.5.4.3],
271 link:RelNotes/1.5.4.2.txt[1.5.4.2],
272 link:RelNotes/1.5.4.1.txt[1.5.4.1],
273 link:RelNotes/1.5.4.txt[1.5.4].
275 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
278 link:RelNotes/1.5.3.8.txt[1.5.3.8],
279 link:RelNotes/1.5.3.7.txt[1.5.3.7],
280 link:RelNotes/1.5.3.6.txt[1.5.3.6],
281 link:RelNotes/1.5.3.5.txt[1.5.3.5],
282 link:RelNotes/1.5.3.4.txt[1.5.3.4],
283 link:RelNotes/1.5.3.3.txt[1.5.3.3],
284 link:RelNotes/1.5.3.2.txt[1.5.3.2],
285 link:RelNotes/1.5.3.1.txt[1.5.3.1],
286 link:RelNotes/1.5.3.txt[1.5.3].
288 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
291 link:RelNotes/1.5.2.5.txt[1.5.2.5],
292 link:RelNotes/1.5.2.4.txt[1.5.2.4],
293 link:RelNotes/1.5.2.3.txt[1.5.2.3],
294 link:RelNotes/1.5.2.2.txt[1.5.2.2],
295 link:RelNotes/1.5.2.1.txt[1.5.2.1],
296 link:RelNotes/1.5.2.txt[1.5.2].
298 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
301 link:RelNotes/1.5.1.6.txt[1.5.1.6],
302 link:RelNotes/1.5.1.5.txt[1.5.1.5],
303 link:RelNotes/1.5.1.4.txt[1.5.1.4],
304 link:RelNotes/1.5.1.3.txt[1.5.1.3],
305 link:RelNotes/1.5.1.2.txt[1.5.1.2],
306 link:RelNotes/1.5.1.1.txt[1.5.1.1],
307 link:RelNotes/1.5.1.txt[1.5.1].
309 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
312 link:RelNotes/1.5.0.7.txt[1.5.0.7],
313 link:RelNotes/1.5.0.6.txt[1.5.0.6],
314 link:RelNotes/1.5.0.5.txt[1.5.0.5],
315 link:RelNotes/1.5.0.3.txt[1.5.0.3],
316 link:RelNotes/1.5.0.2.txt[1.5.0.2],
317 link:RelNotes/1.5.0.1.txt[1.5.0.1],
318 link:RelNotes/1.5.0.txt[1.5.0].
320 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
321 link:v1.3.3/git.html[1.3.3],
322 link:v1.2.6/git.html[1.2.6],
323 link:v1.0.13/git.html[1.0.13].
332 Prints the git suite version that the 'git' program came from.
335 Prints the synopsis and a list of the most commonly used
336 commands. If the option '--all' or '-a' is given then all
337 available commands are printed. If a git command is named this
338 option will bring up the manual page for that command.
340 Other options are available to control how the manual page is
341 displayed. See linkgit:git-help[1] for more information,
342 because `git --help ...` is converted internally into `git
346 Pass a configuration parameter to the command. The value
347 given will override values from configuration files.
348 The <name> is expected in the same format as listed by
349 'git config' (subkeys separated by dots).
351 --exec-path[=<path>]::
352 Path to wherever your core git programs are installed.
353 This can also be controlled by setting the GIT_EXEC_PATH
354 environment variable. If no path is given, 'git' will print
355 the current setting and then exit.
358 Print the path, without trailing slash, where git's HTML
359 documentation is installed and exit.
362 Print the manpath (see `man(1)`) for the man pages for
363 this version of git and exit.
366 Print the path where the Info files documenting this
367 version of git are installed and exit.
371 Pipe all output into 'less' (or if set, $PAGER) if standard
372 output is a terminal. This overrides the `pager.<cmd>`
373 configuration options (see the "Configuration Mechanism" section
377 Do not pipe git output into a pager.
380 Set the path to the repository. This can also be controlled by
381 setting the GIT_DIR environment variable. It can be an absolute
382 path or relative path to current working directory.
385 Set the path to the working tree. It can be an absolute path
386 or a path relative to the current working directory.
387 This can also be controlled by setting the GIT_WORK_TREE
388 environment variable and the core.worktree configuration
389 variable (see core.worktree in linkgit:git-config[1] for a
390 more detailed discussion).
393 Set the git namespace. See linkgit:gitnamespaces[7] for more
394 details. Equivalent to setting the `GIT_NAMESPACE` environment
398 Treat the repository as a bare repository. If GIT_DIR
399 environment is not set, it is set to the current working
402 --no-replace-objects::
403 Do not use replacement refs to replace git objects. See
404 linkgit:git-replace[1] for more information.
407 FURTHER DOCUMENTATION
408 ---------------------
410 See the references above to get started using git. The following is
411 probably more detail than necessary for a first-time user.
413 The link:user-manual.html#git-concepts[git concepts chapter of the
414 user-manual] and linkgit:gitcore-tutorial[7] both provide
415 introductions to the underlying git architecture.
417 See linkgit:gitworkflows[7] for an overview of recommended workflows.
419 See also the link:howto-index.html[howto] documents for some useful
422 The internals are documented in the
423 link:technical/api-index.html[GIT API documentation].
428 We divide git into high level ("porcelain") commands and low level
429 ("plumbing") commands.
431 High-level commands (porcelain)
432 -------------------------------
434 We separate the porcelain commands into the main commands and some
435 ancillary user utilities.
437 Main porcelain commands
438 ~~~~~~~~~~~~~~~~~~~~~~~
440 include::cmds-mainporcelain.txt[]
446 include::cmds-ancillarymanipulators.txt[]
450 include::cmds-ancillaryinterrogators.txt[]
453 Interacting with Others
454 ~~~~~~~~~~~~~~~~~~~~~~~
456 These commands are to interact with foreign SCM and with other
457 people via patch over e-mail.
459 include::cmds-foreignscminterface.txt[]
462 Low-level commands (plumbing)
463 -----------------------------
465 Although git includes its
466 own porcelain layer, its low-level commands are sufficient to support
467 development of alternative porcelains. Developers of such porcelains
468 might start by reading about linkgit:git-update-index[1] and
469 linkgit:git-read-tree[1].
471 The interface (input, output, set of options and the semantics)
472 to these low-level commands are meant to be a lot more stable
473 than Porcelain level commands, because these commands are
474 primarily for scripted use. The interface to Porcelain commands
475 on the other hand are subject to change in order to improve the
478 The following description divides
479 the low-level commands into commands that manipulate objects (in
480 the repository, index, and working tree), commands that interrogate and
481 compare objects, and commands that move objects and references between
485 Manipulation commands
486 ~~~~~~~~~~~~~~~~~~~~~
488 include::cmds-plumbingmanipulators.txt[]
491 Interrogation commands
492 ~~~~~~~~~~~~~~~~~~~~~~
494 include::cmds-plumbinginterrogators.txt[]
496 In general, the interrogate commands do not touch the files in
500 Synching repositories
501 ~~~~~~~~~~~~~~~~~~~~~
503 include::cmds-synchingrepositories.txt[]
505 The following are helper commands used by the above; end users
506 typically do not use them directly.
508 include::cmds-synchelpers.txt[]
511 Internal helper commands
512 ~~~~~~~~~~~~~~~~~~~~~~~~
514 These are internal helper commands used by other commands; end
515 users typically do not use them directly.
517 include::cmds-purehelpers.txt[]
520 Configuration Mechanism
521 -----------------------
523 Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
524 is used to hold per-repository configuration options. It is a
525 simple text file modeled after `.ini` format familiar to some
526 people. Here is an example:
530 # A '#' or ';' character indicates a comment.
535 ; Don't trust file modes
540 name = "Junio C Hamano"
541 email = "junkio@twinsun.com"
545 Various commands read from the configuration file and adjust
546 their operation accordingly. See linkgit:git-config[1] for a
550 Identifier Terminology
551 ----------------------
553 Indicates the object name for any type of object.
556 Indicates a blob object name.
559 Indicates a tree object name.
562 Indicates a commit object name.
565 Indicates a tree, commit or tag object name. A
566 command that takes a <tree-ish> argument ultimately wants to
567 operate on a <tree> object but automatically dereferences
568 <commit> and <tag> objects that point at a <tree>.
571 Indicates a commit or tag object name. A
572 command that takes a <commit-ish> argument ultimately wants to
573 operate on a <commit> object but automatically dereferences
574 <tag> objects that point at a <commit>.
577 Indicates that an object type is required.
578 Currently one of: `blob`, `tree`, `commit`, or `tag`.
581 Indicates a filename - almost always relative to the
582 root of the tree structure `GIT_INDEX_FILE` describes.
586 Any git command accepting any <object> can also use the following
590 indicates the head of the current branch.
594 (i.e. a `refs/tags/<tag>` reference).
598 (i.e. a `refs/heads/<head>` reference).
600 For a more complete list of ways to spell object names, see
601 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
604 File/Directory Structure
605 ------------------------
607 Please see the linkgit:gitrepository-layout[5] document.
609 Read linkgit:githooks[5] for more details about each hook.
611 Higher level SCMs may provide and manage additional information in the
617 Please see linkgit:gitglossary[7].
620 Environment Variables
621 ---------------------
622 Various git commands use the following environment variables:
626 These environment variables apply to 'all' core git commands. Nb: it
627 is worth noting that they may be used/overridden by SCMS sitting above
628 git so take care if using Cogito etc.
631 This environment allows the specification of an alternate
632 index file. If not specified, the default of `$GIT_DIR/index`
635 'GIT_OBJECT_DIRECTORY'::
636 If the object storage directory is specified via this
637 environment variable then the sha1 directories are created
638 underneath - otherwise the default `$GIT_DIR/objects`
641 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
642 Due to the immutable nature of git objects, old objects can be
643 archived into shared, read-only directories. This variable
644 specifies a ":" separated (on Windows ";" separated) list
645 of git object directories which can be used to search for git
646 objects. New objects will not be written to these directories.
649 If the 'GIT_DIR' environment variable is set then it
650 specifies a path to use instead of the default `.git`
651 for the base of the repository.
654 Set the path to the working tree. The value will not be
655 used in combination with repositories found automatically in
656 a .git directory (i.e. $GIT_DIR is not set).
657 This can also be controlled by the '--work-tree' command line
658 option and the core.worktree configuration variable.
661 Set the git namespace; see linkgit:gitnamespaces[7] for details.
662 The '--namespace' command-line option also sets this value.
664 'GIT_CEILING_DIRECTORIES'::
665 This should be a colon-separated list of absolute paths.
666 If set, it is a list of directories that git should not chdir
667 up into while looking for a repository directory.
668 It will not exclude the current working directory or
669 a GIT_DIR set on the command line or in the environment.
670 (Useful for excluding slow-loading network directories.)
672 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
673 When run in a directory that does not have ".git" repository
674 directory, git tries to find such a directory in the parent
675 directories to find the top of the working tree, but by default it
676 does not cross filesystem boundaries. This environment variable
677 can be set to true to tell git not to stop at filesystem
678 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
679 an explicit repository directory set via 'GIT_DIR' or on the
687 'GIT_COMMITTER_NAME'::
688 'GIT_COMMITTER_EMAIL'::
689 'GIT_COMMITTER_DATE'::
691 see linkgit:git-commit-tree[1]
696 Only valid setting is "--unified=??" or "-u??" to set the
697 number of context lines shown when a unified diff is created.
698 This takes precedence over any "-U" or "--unified" option
699 value passed on the git diff command line.
701 'GIT_EXTERNAL_DIFF'::
702 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
703 program named by it is called, instead of the diff invocation
704 described above. For a path that is added, removed, or modified,
705 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
707 path old-file old-hex old-mode new-file new-hex new-mode
711 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
712 contents of <old|new>,
713 <old|new>-hex:: are the 40-hexdigit SHA1 hashes,
714 <old|new>-mode:: are the octal representation of the file modes.
716 The file parameters can point at the user's working file
717 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
718 when a new file is added), or a temporary file (e.g. `old-file` in the
719 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
720 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
722 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
727 'GIT_MERGE_VERBOSITY'::
728 A number controlling the amount of output shown by
729 the recursive merge strategy. Overrides merge.verbosity.
730 See linkgit:git-merge[1]
733 This environment variable overrides `$PAGER`. If it is set
734 to an empty string or to the value "cat", git will not launch
735 a pager. See also the `core.pager` option in
736 linkgit:git-config[1].
739 This environment variable overrides `$EDITOR` and `$VISUAL`.
740 It is used by several git commands when, on interactive mode,
741 an editor is to be launched. See also linkgit:git-var[1]
742 and the `core.editor` option in linkgit:git-config[1].
745 If this environment variable is set then 'git fetch'
746 and 'git push' will use this command instead
747 of 'ssh' when they need to connect to a remote system.
748 The '$GIT_SSH' command will be given exactly two arguments:
749 the 'username@host' (or just 'host') from the URL and the
750 shell command to execute on that remote system.
752 To pass options to the program that you want to list in GIT_SSH
753 you will need to wrap the program and options into a shell script,
754 then set GIT_SSH to refer to the shell script.
756 Usually it is easier to configure any desired options through your
757 personal `.ssh/config` file. Please consult your ssh documentation
761 If this environment variable is set, then git commands which need to
762 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
763 will call this program with a suitable prompt as command line argument
764 and read the password from its STDOUT. See also the 'core.askpass'
765 option in linkgit:git-config[1].
768 If this environment variable is set to "1", then commands such
769 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
770 and 'git whatchanged' will force a flush of the output stream
771 after each commit-oriented record have been flushed. If this
772 variable is set to "0", the output of these commands will be done
773 using completely buffered I/O. If this environment variable is
774 not set, git will choose buffered or record-oriented flushing
775 based on whether stdout appears to be redirected to a file or not.
778 If this variable is set to "1", "2" or "true" (comparison
779 is case insensitive), git will print `trace:` messages on
780 stderr telling about alias expansion, built-in command
781 execution and external command execution.
782 If this variable is set to an integer value greater than 1
783 and lower than 10 (strictly) then git will interpret this
784 value as an open file descriptor and will try to write the
785 trace messages into this file descriptor.
786 Alternatively, if this variable is set to an absolute path
787 (starting with a '/' character), git will interpret this
788 as a file path and will try to write the trace messages
791 Discussion[[Discussion]]
792 ------------------------
794 More detail on the following is available from the
795 link:user-manual.html#git-concepts[git concepts chapter of the
796 user-manual] and linkgit:gitcore-tutorial[7].
798 A git project normally consists of a working directory with a ".git"
799 subdirectory at the top level. The .git directory contains, among other
800 things, a compressed object database representing the complete history
801 of the project, an "index" file which links that history to the current
802 contents of the working tree, and named pointers into that history such
803 as tags and branch heads.
805 The object database contains objects of three main types: blobs, which
806 hold file data; trees, which point to blobs and other trees to build up
807 directory hierarchies; and commits, which each reference a single tree
808 and some number of parent commits.
810 The commit, equivalent to what other systems call a "changeset" or
811 "version", represents a step in the project's history, and each parent
812 represents an immediately preceding step. Commits with more than one
813 parent represent merges of independent lines of development.
815 All objects are named by the SHA1 hash of their contents, normally
816 written as a string of 40 hex digits. Such names are globally unique.
817 The entire history leading up to a commit can be vouched for by signing
818 just that commit. A fourth object type, the tag, is provided for this
821 When first created, objects are stored in individual files, but for
822 efficiency may later be compressed together into "pack files".
824 Named pointers called refs mark interesting points in history. A ref
825 may contain the SHA1 name of an object or the name of another ref. Refs
826 with names beginning `ref/head/` contain the SHA1 name of the most
827 recent commit (or "head") of a branch under development. SHA1 names of
828 tags of interest are stored under `ref/tags/`. A special ref named
829 `HEAD` contains the name of the currently checked-out branch.
831 The index file is initialized with a list of all paths and, for each
832 path, a blob object and a set of attributes. The blob object represents
833 the contents of the file as of the head of the current branch. The
834 attributes (last modified time, size, etc.) are taken from the
835 corresponding file in the working tree. Subsequent changes to the
836 working tree can be found by comparing these attributes. The index may
837 be updated with new content, and new commits may be created from the
838 content stored in the index.
840 The index is also capable of storing multiple entries (called "stages")
841 for a given pathname. These stages are used to hold the various
842 unmerged version of a file when a merge is in progress.
846 Git was started by Linus Torvalds, and is currently maintained by Junio
847 C Hamano. Numerous contributions have come from the git mailing list
848 <git@vger.kernel.org>. For a more complete list of contributors, see
849 http://git-scm.com/about. If you have a clone of git.git itself, the
850 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
851 the authors for specific parts of the project.
856 Report bugs to the Git mailing list <git@vger.kernel.org> where the
857 development and maintenance is primarily done. You do not have to be
858 subscribed to the list to send a message there.
862 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
863 link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7],
864 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
865 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
866 linkgit:gitworkflows[7]
870 Part of the linkgit:git[1] suite