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.4/git.html[documentation for release 1.7.11.4]
50 link:RelNotes/1.7.11.4.txt[1.7.11.4],
51 link:RelNotes/1.7.11.3.txt[1.7.11.3],
52 link:RelNotes/1.7.11.2.txt[1.7.11.2],
53 link:RelNotes/1.7.11.1.txt[1.7.11.1],
54 link:RelNotes/1.7.11.txt[1.7.11].
56 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
59 link:RelNotes/1.7.10.5.txt[1.7.10.5],
60 link:RelNotes/1.7.10.4.txt[1.7.10.4],
61 link:RelNotes/1.7.10.3.txt[1.7.10.3],
62 link:RelNotes/1.7.10.2.txt[1.7.10.2],
63 link:RelNotes/1.7.10.1.txt[1.7.10.1],
64 link:RelNotes/1.7.10.txt[1.7.10].
66 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
69 link:RelNotes/1.7.9.7.txt[1.7.9.7],
70 link:RelNotes/1.7.9.6.txt[1.7.9.6],
71 link:RelNotes/1.7.9.5.txt[1.7.9.5],
72 link:RelNotes/1.7.9.4.txt[1.7.9.4],
73 link:RelNotes/1.7.9.3.txt[1.7.9.3],
74 link:RelNotes/1.7.9.2.txt[1.7.9.2],
75 link:RelNotes/1.7.9.1.txt[1.7.9.1],
76 link:RelNotes/1.7.9.txt[1.7.9].
78 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
81 link:RelNotes/1.7.8.6.txt[1.7.8.6],
82 link:RelNotes/1.7.8.5.txt[1.7.8.5],
83 link:RelNotes/1.7.8.4.txt[1.7.8.4],
84 link:RelNotes/1.7.8.3.txt[1.7.8.3],
85 link:RelNotes/1.7.8.2.txt[1.7.8.2],
86 link:RelNotes/1.7.8.1.txt[1.7.8.1],
87 link:RelNotes/1.7.8.txt[1.7.8].
89 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
92 link:RelNotes/1.7.7.7.txt[1.7.7.7],
93 link:RelNotes/1.7.7.6.txt[1.7.7.6],
94 link:RelNotes/1.7.7.5.txt[1.7.7.5],
95 link:RelNotes/1.7.7.4.txt[1.7.7.4],
96 link:RelNotes/1.7.7.3.txt[1.7.7.3],
97 link:RelNotes/1.7.7.2.txt[1.7.7.2],
98 link:RelNotes/1.7.7.1.txt[1.7.7.1],
99 link:RelNotes/1.7.7.txt[1.7.7].
101 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
104 link:RelNotes/1.7.6.6.txt[1.7.6.6],
105 link:RelNotes/1.7.6.5.txt[1.7.6.5],
106 link:RelNotes/1.7.6.4.txt[1.7.6.4],
107 link:RelNotes/1.7.6.3.txt[1.7.6.3],
108 link:RelNotes/1.7.6.2.txt[1.7.6.2],
109 link:RelNotes/1.7.6.1.txt[1.7.6.1],
110 link:RelNotes/1.7.6.txt[1.7.6].
112 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
115 link:RelNotes/1.7.5.4.txt[1.7.5.4],
116 link:RelNotes/1.7.5.3.txt[1.7.5.3],
117 link:RelNotes/1.7.5.2.txt[1.7.5.2],
118 link:RelNotes/1.7.5.1.txt[1.7.5.1],
119 link:RelNotes/1.7.5.txt[1.7.5].
121 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
124 link:RelNotes/1.7.4.5.txt[1.7.4.5],
125 link:RelNotes/1.7.4.4.txt[1.7.4.4],
126 link:RelNotes/1.7.4.3.txt[1.7.4.3],
127 link:RelNotes/1.7.4.2.txt[1.7.4.2],
128 link:RelNotes/1.7.4.1.txt[1.7.4.1],
129 link:RelNotes/1.7.4.txt[1.7.4].
131 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
134 link:RelNotes/1.7.3.5.txt[1.7.3.5],
135 link:RelNotes/1.7.3.4.txt[1.7.3.4],
136 link:RelNotes/1.7.3.3.txt[1.7.3.3],
137 link:RelNotes/1.7.3.2.txt[1.7.3.2],
138 link:RelNotes/1.7.3.1.txt[1.7.3.1],
139 link:RelNotes/1.7.3.txt[1.7.3].
141 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
144 link:RelNotes/1.7.2.5.txt[1.7.2.5],
145 link:RelNotes/1.7.2.4.txt[1.7.2.4],
146 link:RelNotes/1.7.2.3.txt[1.7.2.3],
147 link:RelNotes/1.7.2.2.txt[1.7.2.2],
148 link:RelNotes/1.7.2.1.txt[1.7.2.1],
149 link:RelNotes/1.7.2.txt[1.7.2].
151 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
154 link:RelNotes/1.7.1.4.txt[1.7.1.4],
155 link:RelNotes/1.7.1.3.txt[1.7.1.3],
156 link:RelNotes/1.7.1.2.txt[1.7.1.2],
157 link:RelNotes/1.7.1.1.txt[1.7.1.1],
158 link:RelNotes/1.7.1.txt[1.7.1].
160 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
163 link:RelNotes/1.7.0.9.txt[1.7.0.9],
164 link:RelNotes/1.7.0.8.txt[1.7.0.8],
165 link:RelNotes/1.7.0.7.txt[1.7.0.7],
166 link:RelNotes/1.7.0.6.txt[1.7.0.6],
167 link:RelNotes/1.7.0.5.txt[1.7.0.5],
168 link:RelNotes/1.7.0.4.txt[1.7.0.4],
169 link:RelNotes/1.7.0.3.txt[1.7.0.3],
170 link:RelNotes/1.7.0.2.txt[1.7.0.2],
171 link:RelNotes/1.7.0.1.txt[1.7.0.1],
172 link:RelNotes/1.7.0.txt[1.7.0].
174 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
177 link:RelNotes/1.6.6.3.txt[1.6.6.3],
178 link:RelNotes/1.6.6.2.txt[1.6.6.2],
179 link:RelNotes/1.6.6.1.txt[1.6.6.1],
180 link:RelNotes/1.6.6.txt[1.6.6].
182 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
185 link:RelNotes/1.6.5.9.txt[1.6.5.9],
186 link:RelNotes/1.6.5.8.txt[1.6.5.8],
187 link:RelNotes/1.6.5.7.txt[1.6.5.7],
188 link:RelNotes/1.6.5.6.txt[1.6.5.6],
189 link:RelNotes/1.6.5.5.txt[1.6.5.5],
190 link:RelNotes/1.6.5.4.txt[1.6.5.4],
191 link:RelNotes/1.6.5.3.txt[1.6.5.3],
192 link:RelNotes/1.6.5.2.txt[1.6.5.2],
193 link:RelNotes/1.6.5.1.txt[1.6.5.1],
194 link:RelNotes/1.6.5.txt[1.6.5].
196 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
199 link:RelNotes/1.6.4.5.txt[1.6.4.5],
200 link:RelNotes/1.6.4.4.txt[1.6.4.4],
201 link:RelNotes/1.6.4.3.txt[1.6.4.3],
202 link:RelNotes/1.6.4.2.txt[1.6.4.2],
203 link:RelNotes/1.6.4.1.txt[1.6.4.1],
204 link:RelNotes/1.6.4.txt[1.6.4].
206 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
209 link:RelNotes/1.6.3.4.txt[1.6.3.4],
210 link:RelNotes/1.6.3.3.txt[1.6.3.3],
211 link:RelNotes/1.6.3.2.txt[1.6.3.2],
212 link:RelNotes/1.6.3.1.txt[1.6.3.1],
213 link:RelNotes/1.6.3.txt[1.6.3].
216 link:RelNotes/1.6.2.5.txt[1.6.2.5],
217 link:RelNotes/1.6.2.4.txt[1.6.2.4],
218 link:RelNotes/1.6.2.3.txt[1.6.2.3],
219 link:RelNotes/1.6.2.2.txt[1.6.2.2],
220 link:RelNotes/1.6.2.1.txt[1.6.2.1],
221 link:RelNotes/1.6.2.txt[1.6.2].
223 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
226 link:RelNotes/1.6.1.3.txt[1.6.1.3],
227 link:RelNotes/1.6.1.2.txt[1.6.1.2],
228 link:RelNotes/1.6.1.1.txt[1.6.1.1],
229 link:RelNotes/1.6.1.txt[1.6.1].
231 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
234 link:RelNotes/1.6.0.6.txt[1.6.0.6],
235 link:RelNotes/1.6.0.5.txt[1.6.0.5],
236 link:RelNotes/1.6.0.4.txt[1.6.0.4],
237 link:RelNotes/1.6.0.3.txt[1.6.0.3],
238 link:RelNotes/1.6.0.2.txt[1.6.0.2],
239 link:RelNotes/1.6.0.1.txt[1.6.0.1],
240 link:RelNotes/1.6.0.txt[1.6.0].
242 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
245 link:RelNotes/1.5.6.6.txt[1.5.6.6],
246 link:RelNotes/1.5.6.5.txt[1.5.6.5],
247 link:RelNotes/1.5.6.4.txt[1.5.6.4],
248 link:RelNotes/1.5.6.3.txt[1.5.6.3],
249 link:RelNotes/1.5.6.2.txt[1.5.6.2],
250 link:RelNotes/1.5.6.1.txt[1.5.6.1],
251 link:RelNotes/1.5.6.txt[1.5.6].
253 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
256 link:RelNotes/1.5.5.6.txt[1.5.5.6],
257 link:RelNotes/1.5.5.5.txt[1.5.5.5],
258 link:RelNotes/1.5.5.4.txt[1.5.5.4],
259 link:RelNotes/1.5.5.3.txt[1.5.5.3],
260 link:RelNotes/1.5.5.2.txt[1.5.5.2],
261 link:RelNotes/1.5.5.1.txt[1.5.5.1],
262 link:RelNotes/1.5.5.txt[1.5.5].
264 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
267 link:RelNotes/1.5.4.7.txt[1.5.4.7],
268 link:RelNotes/1.5.4.6.txt[1.5.4.6],
269 link:RelNotes/1.5.4.5.txt[1.5.4.5],
270 link:RelNotes/1.5.4.4.txt[1.5.4.4],
271 link:RelNotes/1.5.4.3.txt[1.5.4.3],
272 link:RelNotes/1.5.4.2.txt[1.5.4.2],
273 link:RelNotes/1.5.4.1.txt[1.5.4.1],
274 link:RelNotes/1.5.4.txt[1.5.4].
276 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
279 link:RelNotes/1.5.3.8.txt[1.5.3.8],
280 link:RelNotes/1.5.3.7.txt[1.5.3.7],
281 link:RelNotes/1.5.3.6.txt[1.5.3.6],
282 link:RelNotes/1.5.3.5.txt[1.5.3.5],
283 link:RelNotes/1.5.3.4.txt[1.5.3.4],
284 link:RelNotes/1.5.3.3.txt[1.5.3.3],
285 link:RelNotes/1.5.3.2.txt[1.5.3.2],
286 link:RelNotes/1.5.3.1.txt[1.5.3.1],
287 link:RelNotes/1.5.3.txt[1.5.3].
289 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
292 link:RelNotes/1.5.2.5.txt[1.5.2.5],
293 link:RelNotes/1.5.2.4.txt[1.5.2.4],
294 link:RelNotes/1.5.2.3.txt[1.5.2.3],
295 link:RelNotes/1.5.2.2.txt[1.5.2.2],
296 link:RelNotes/1.5.2.1.txt[1.5.2.1],
297 link:RelNotes/1.5.2.txt[1.5.2].
299 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
302 link:RelNotes/1.5.1.6.txt[1.5.1.6],
303 link:RelNotes/1.5.1.5.txt[1.5.1.5],
304 link:RelNotes/1.5.1.4.txt[1.5.1.4],
305 link:RelNotes/1.5.1.3.txt[1.5.1.3],
306 link:RelNotes/1.5.1.2.txt[1.5.1.2],
307 link:RelNotes/1.5.1.1.txt[1.5.1.1],
308 link:RelNotes/1.5.1.txt[1.5.1].
310 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
313 link:RelNotes/1.5.0.7.txt[1.5.0.7],
314 link:RelNotes/1.5.0.6.txt[1.5.0.6],
315 link:RelNotes/1.5.0.5.txt[1.5.0.5],
316 link:RelNotes/1.5.0.3.txt[1.5.0.3],
317 link:RelNotes/1.5.0.2.txt[1.5.0.2],
318 link:RelNotes/1.5.0.1.txt[1.5.0.1],
319 link:RelNotes/1.5.0.txt[1.5.0].
321 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
322 link:v1.3.3/git.html[1.3.3],
323 link:v1.2.6/git.html[1.2.6],
324 link:v1.0.13/git.html[1.0.13].
333 Prints the git suite version that the 'git' program came from.
336 Prints the synopsis and a list of the most commonly used
337 commands. If the option '--all' or '-a' is given then all
338 available commands are printed. If a git command is named this
339 option will bring up the manual page for that command.
341 Other options are available to control how the manual page is
342 displayed. See linkgit:git-help[1] for more information,
343 because `git --help ...` is converted internally into `git
347 Pass a configuration parameter to the command. The value
348 given will override values from configuration files.
349 The <name> is expected in the same format as listed by
350 'git config' (subkeys separated by dots).
352 --exec-path[=<path>]::
353 Path to wherever your core git programs are installed.
354 This can also be controlled by setting the GIT_EXEC_PATH
355 environment variable. If no path is given, 'git' will print
356 the current setting and then exit.
359 Print the path, without trailing slash, where git's HTML
360 documentation is installed and exit.
363 Print the manpath (see `man(1)`) for the man pages for
364 this version of git and exit.
367 Print the path where the Info files documenting this
368 version of git are installed and exit.
372 Pipe all output into 'less' (or if set, $PAGER) if standard
373 output is a terminal. This overrides the `pager.<cmd>`
374 configuration options (see the "Configuration Mechanism" section
378 Do not pipe git output into a pager.
381 Set the path to the repository. This can also be controlled by
382 setting the GIT_DIR environment variable. It can be an absolute
383 path or relative path to current working directory.
386 Set the path to the working tree. It can be an absolute path
387 or a path relative to the current working directory.
388 This can also be controlled by setting the GIT_WORK_TREE
389 environment variable and the core.worktree configuration
390 variable (see core.worktree in linkgit:git-config[1] for a
391 more detailed discussion).
394 Set the git namespace. See linkgit:gitnamespaces[7] for more
395 details. Equivalent to setting the `GIT_NAMESPACE` environment
399 Treat the repository as a bare repository. If GIT_DIR
400 environment is not set, it is set to the current working
403 --no-replace-objects::
404 Do not use replacement refs to replace git objects. See
405 linkgit:git-replace[1] for more information.
408 FURTHER DOCUMENTATION
409 ---------------------
411 See the references above to get started using git. The following is
412 probably more detail than necessary for a first-time user.
414 The link:user-manual.html#git-concepts[git concepts chapter of the
415 user-manual] and linkgit:gitcore-tutorial[7] both provide
416 introductions to the underlying git architecture.
418 See linkgit:gitworkflows[7] for an overview of recommended workflows.
420 See also the link:howto-index.html[howto] documents for some useful
423 The internals are documented in the
424 link:technical/api-index.html[GIT API documentation].
429 We divide git into high level ("porcelain") commands and low level
430 ("plumbing") commands.
432 High-level commands (porcelain)
433 -------------------------------
435 We separate the porcelain commands into the main commands and some
436 ancillary user utilities.
438 Main porcelain commands
439 ~~~~~~~~~~~~~~~~~~~~~~~
441 include::cmds-mainporcelain.txt[]
447 include::cmds-ancillarymanipulators.txt[]
451 include::cmds-ancillaryinterrogators.txt[]
454 Interacting with Others
455 ~~~~~~~~~~~~~~~~~~~~~~~
457 These commands are to interact with foreign SCM and with other
458 people via patch over e-mail.
460 include::cmds-foreignscminterface.txt[]
463 Low-level commands (plumbing)
464 -----------------------------
466 Although git includes its
467 own porcelain layer, its low-level commands are sufficient to support
468 development of alternative porcelains. Developers of such porcelains
469 might start by reading about linkgit:git-update-index[1] and
470 linkgit:git-read-tree[1].
472 The interface (input, output, set of options and the semantics)
473 to these low-level commands are meant to be a lot more stable
474 than Porcelain level commands, because these commands are
475 primarily for scripted use. The interface to Porcelain commands
476 on the other hand are subject to change in order to improve the
479 The following description divides
480 the low-level commands into commands that manipulate objects (in
481 the repository, index, and working tree), commands that interrogate and
482 compare objects, and commands that move objects and references between
486 Manipulation commands
487 ~~~~~~~~~~~~~~~~~~~~~
489 include::cmds-plumbingmanipulators.txt[]
492 Interrogation commands
493 ~~~~~~~~~~~~~~~~~~~~~~
495 include::cmds-plumbinginterrogators.txt[]
497 In general, the interrogate commands do not touch the files in
501 Synching repositories
502 ~~~~~~~~~~~~~~~~~~~~~
504 include::cmds-synchingrepositories.txt[]
506 The following are helper commands used by the above; end users
507 typically do not use them directly.
509 include::cmds-synchelpers.txt[]
512 Internal helper commands
513 ~~~~~~~~~~~~~~~~~~~~~~~~
515 These are internal helper commands used by other commands; end
516 users typically do not use them directly.
518 include::cmds-purehelpers.txt[]
521 Configuration Mechanism
522 -----------------------
524 Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
525 is used to hold per-repository configuration options. It is a
526 simple text file modeled after `.ini` format familiar to some
527 people. Here is an example:
531 # A '#' or ';' character indicates a comment.
536 ; Don't trust file modes
541 name = "Junio C Hamano"
542 email = "junkio@twinsun.com"
546 Various commands read from the configuration file and adjust
547 their operation accordingly. See linkgit:git-config[1] for a
551 Identifier Terminology
552 ----------------------
554 Indicates the object name for any type of object.
557 Indicates a blob object name.
560 Indicates a tree object name.
563 Indicates a commit object name.
566 Indicates a tree, commit or tag object name. A
567 command that takes a <tree-ish> argument ultimately wants to
568 operate on a <tree> object but automatically dereferences
569 <commit> and <tag> objects that point at a <tree>.
572 Indicates a commit or tag object name. A
573 command that takes a <commit-ish> argument ultimately wants to
574 operate on a <commit> object but automatically dereferences
575 <tag> objects that point at a <commit>.
578 Indicates that an object type is required.
579 Currently one of: `blob`, `tree`, `commit`, or `tag`.
582 Indicates a filename - almost always relative to the
583 root of the tree structure `GIT_INDEX_FILE` describes.
587 Any git command accepting any <object> can also use the following
591 indicates the head of the current branch.
595 (i.e. a `refs/tags/<tag>` reference).
599 (i.e. a `refs/heads/<head>` reference).
601 For a more complete list of ways to spell object names, see
602 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
605 File/Directory Structure
606 ------------------------
608 Please see the linkgit:gitrepository-layout[5] document.
610 Read linkgit:githooks[5] for more details about each hook.
612 Higher level SCMs may provide and manage additional information in the
618 Please see linkgit:gitglossary[7].
621 Environment Variables
622 ---------------------
623 Various git commands use the following environment variables:
627 These environment variables apply to 'all' core git commands. Nb: it
628 is worth noting that they may be used/overridden by SCMS sitting above
629 git so take care if using Cogito etc.
632 This environment allows the specification of an alternate
633 index file. If not specified, the default of `$GIT_DIR/index`
636 'GIT_OBJECT_DIRECTORY'::
637 If the object storage directory is specified via this
638 environment variable then the sha1 directories are created
639 underneath - otherwise the default `$GIT_DIR/objects`
642 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
643 Due to the immutable nature of git objects, old objects can be
644 archived into shared, read-only directories. This variable
645 specifies a ":" separated (on Windows ";" separated) list
646 of git object directories which can be used to search for git
647 objects. New objects will not be written to these directories.
650 If the 'GIT_DIR' environment variable is set then it
651 specifies a path to use instead of the default `.git`
652 for the base of the repository.
655 Set the path to the working tree. The value will not be
656 used in combination with repositories found automatically in
657 a .git directory (i.e. $GIT_DIR is not set).
658 This can also be controlled by the '--work-tree' command line
659 option and the core.worktree configuration variable.
662 Set the git namespace; see linkgit:gitnamespaces[7] for details.
663 The '--namespace' command-line option also sets this value.
665 'GIT_CEILING_DIRECTORIES'::
666 This should be a colon-separated list of absolute paths.
667 If set, it is a list of directories that git should not chdir
668 up into while looking for a repository directory.
669 It will not exclude the current working directory or
670 a GIT_DIR set on the command line or in the environment.
671 (Useful for excluding slow-loading network directories.)
673 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
674 When run in a directory that does not have ".git" repository
675 directory, git tries to find such a directory in the parent
676 directories to find the top of the working tree, but by default it
677 does not cross filesystem boundaries. This environment variable
678 can be set to true to tell git not to stop at filesystem
679 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
680 an explicit repository directory set via 'GIT_DIR' or on the
688 'GIT_COMMITTER_NAME'::
689 'GIT_COMMITTER_EMAIL'::
690 'GIT_COMMITTER_DATE'::
692 see linkgit:git-commit-tree[1]
697 Only valid setting is "--unified=??" or "-u??" to set the
698 number of context lines shown when a unified diff is created.
699 This takes precedence over any "-U" or "--unified" option
700 value passed on the git diff command line.
702 'GIT_EXTERNAL_DIFF'::
703 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
704 program named by it is called, instead of the diff invocation
705 described above. For a path that is added, removed, or modified,
706 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
708 path old-file old-hex old-mode new-file new-hex new-mode
712 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
713 contents of <old|new>,
714 <old|new>-hex:: are the 40-hexdigit SHA1 hashes,
715 <old|new>-mode:: are the octal representation of the file modes.
717 The file parameters can point at the user's working file
718 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
719 when a new file is added), or a temporary file (e.g. `old-file` in the
720 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
721 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
723 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
728 'GIT_MERGE_VERBOSITY'::
729 A number controlling the amount of output shown by
730 the recursive merge strategy. Overrides merge.verbosity.
731 See linkgit:git-merge[1]
734 This environment variable overrides `$PAGER`. If it is set
735 to an empty string or to the value "cat", git will not launch
736 a pager. See also the `core.pager` option in
737 linkgit:git-config[1].
740 This environment variable overrides `$EDITOR` and `$VISUAL`.
741 It is used by several git commands when, on interactive mode,
742 an editor is to be launched. See also linkgit:git-var[1]
743 and the `core.editor` option in linkgit:git-config[1].
746 If this environment variable is set then 'git fetch'
747 and 'git push' will use this command instead
748 of 'ssh' when they need to connect to a remote system.
749 The '$GIT_SSH' command will be given exactly two arguments:
750 the 'username@host' (or just 'host') from the URL and the
751 shell command to execute on that remote system.
753 To pass options to the program that you want to list in GIT_SSH
754 you will need to wrap the program and options into a shell script,
755 then set GIT_SSH to refer to the shell script.
757 Usually it is easier to configure any desired options through your
758 personal `.ssh/config` file. Please consult your ssh documentation
762 If this environment variable is set, then git commands which need to
763 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
764 will call this program with a suitable prompt as command line argument
765 and read the password from its STDOUT. See also the 'core.askpass'
766 option in linkgit:git-config[1].
769 If this environment variable is set to "1", then commands such
770 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
771 and 'git whatchanged' will force a flush of the output stream
772 after each commit-oriented record have been flushed. If this
773 variable is set to "0", the output of these commands will be done
774 using completely buffered I/O. If this environment variable is
775 not set, git will choose buffered or record-oriented flushing
776 based on whether stdout appears to be redirected to a file or not.
779 If this variable is set to "1", "2" or "true" (comparison
780 is case insensitive), git will print `trace:` messages on
781 stderr telling about alias expansion, built-in command
782 execution and external command execution.
783 If this variable is set to an integer value greater than 1
784 and lower than 10 (strictly) then git will interpret this
785 value as an open file descriptor and will try to write the
786 trace messages into this file descriptor.
787 Alternatively, if this variable is set to an absolute path
788 (starting with a '/' character), git will interpret this
789 as a file path and will try to write the trace messages
792 Discussion[[Discussion]]
793 ------------------------
795 More detail on the following is available from the
796 link:user-manual.html#git-concepts[git concepts chapter of the
797 user-manual] and linkgit:gitcore-tutorial[7].
799 A git project normally consists of a working directory with a ".git"
800 subdirectory at the top level. The .git directory contains, among other
801 things, a compressed object database representing the complete history
802 of the project, an "index" file which links that history to the current
803 contents of the working tree, and named pointers into that history such
804 as tags and branch heads.
806 The object database contains objects of three main types: blobs, which
807 hold file data; trees, which point to blobs and other trees to build up
808 directory hierarchies; and commits, which each reference a single tree
809 and some number of parent commits.
811 The commit, equivalent to what other systems call a "changeset" or
812 "version", represents a step in the project's history, and each parent
813 represents an immediately preceding step. Commits with more than one
814 parent represent merges of independent lines of development.
816 All objects are named by the SHA1 hash of their contents, normally
817 written as a string of 40 hex digits. Such names are globally unique.
818 The entire history leading up to a commit can be vouched for by signing
819 just that commit. A fourth object type, the tag, is provided for this
822 When first created, objects are stored in individual files, but for
823 efficiency may later be compressed together into "pack files".
825 Named pointers called refs mark interesting points in history. A ref
826 may contain the SHA1 name of an object or the name of another ref. Refs
827 with names beginning `ref/head/` contain the SHA1 name of the most
828 recent commit (or "head") of a branch under development. SHA1 names of
829 tags of interest are stored under `ref/tags/`. A special ref named
830 `HEAD` contains the name of the currently checked-out branch.
832 The index file is initialized with a list of all paths and, for each
833 path, a blob object and a set of attributes. The blob object represents
834 the contents of the file as of the head of the current branch. The
835 attributes (last modified time, size, etc.) are taken from the
836 corresponding file in the working tree. Subsequent changes to the
837 working tree can be found by comparing these attributes. The index may
838 be updated with new content, and new commits may be created from the
839 content stored in the index.
841 The index is also capable of storing multiple entries (called "stages")
842 for a given pathname. These stages are used to hold the various
843 unmerged version of a file when a merge is in progress.
847 Git was started by Linus Torvalds, and is currently maintained by Junio
848 C Hamano. Numerous contributions have come from the git mailing list
849 <git@vger.kernel.org>. For a more complete list of contributors, see
850 http://git-scm.com/about. If you have a clone of git.git itself, the
851 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
852 the authors for specific parts of the project.
857 Report bugs to the Git mailing list <git@vger.kernel.org> where the
858 development and maintenance is primarily done. You do not have to be
859 subscribed to the list to send a message there.
863 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
864 link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7],
865 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
866 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
867 linkgit:gitworkflows[7]
871 Part of the linkgit:git[1] suite