1git(1) 2====== 3 4NAME 5---- 6git - the stupid content tracker 7 8 9SYNOPSIS 10-------- 11[verse] 12'git' [--version] [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path] 13 [-p|--paginate|--no-pager] [--no-replace-objects] 14 [--bare] [--git-dir=<path>] [--work-tree=<path>] 15 [-c <name>=<value>] 16 [--help] <command> [<args>] 17 18DESCRIPTION 19----------- 20Git is a fast, scalable, distributed revision control system with an 21unusually rich command set that provides both high-level operations 22and full access to internals. 23 24See linkgit:gittutorial[7] to get started, then see 25link:everyday.html[Everyday Git] for a useful minimum set of commands, and 26"man git-commandname" for documentation of each command. CVS users may 27also want to read linkgit:gitcvs-migration[7]. See 28the link:user-manual.html[Git User's Manual] for a more in-depth 29introduction. 30 31The '<command>' is either a name of a Git command (see below) or an alias 32as defined in the configuration file (see linkgit:git-config[1]). 33 34Formatted and hyperlinked version of the latest git 35documentation can be viewed at 36`http://www.kernel.org/pub/software/scm/git/docs/`. 37 38ifdef::stalenotes[] 39[NOTE] 40============ 41 42You are reading the documentation for the latest (possibly 43unreleased) version of git, that is available from 'master' 44branch of the `git.git` repository. 45Documentation for older releases are available here: 46 47* link:v1.7.5.2/git.html[documentation for release 1.7.5.2] 48 49* release notes for 50 link:RelNotes/1.7.5.2.txt[1.7.5.2], 51 link:RelNotes/1.7.5.1.txt[1.7.5.1], 52 link:RelNotes/1.7.5.txt[1.7.5]. 53 54* link:v1.7.4.5/git.html[documentation for release 1.7.4.5] 55 56* release notes for 57 link:RelNotes/1.7.4.5.txt[1.7.4.5], 58 link:RelNotes/1.7.4.4.txt[1.7.4.4], 59 link:RelNotes/1.7.4.3.txt[1.7.4.3], 60 link:RelNotes/1.7.4.2.txt[1.7.4.2], 61 link:RelNotes/1.7.4.1.txt[1.7.4.1], 62 link:RelNotes/1.7.4.txt[1.7.4]. 63 64* link:v1.7.3.5/git.html[documentation for release 1.7.3.5] 65 66* release notes for 67 link:RelNotes/1.7.3.5.txt[1.7.3.5], 68 link:RelNotes/1.7.3.4.txt[1.7.3.4], 69 link:RelNotes/1.7.3.3.txt[1.7.3.3], 70 link:RelNotes/1.7.3.2.txt[1.7.3.2], 71 link:RelNotes/1.7.3.1.txt[1.7.3.1], 72 link:RelNotes/1.7.3.txt[1.7.3]. 73 74* link:v1.7.2.5/git.html[documentation for release 1.7.2.5] 75 76* release notes for 77 link:RelNotes/1.7.2.5.txt[1.7.2.5], 78 link:RelNotes/1.7.2.4.txt[1.7.2.4], 79 link:RelNotes/1.7.2.3.txt[1.7.2.3], 80 link:RelNotes/1.7.2.2.txt[1.7.2.2], 81 link:RelNotes/1.7.2.1.txt[1.7.2.1], 82 link:RelNotes/1.7.2.txt[1.7.2]. 83 84* link:v1.7.1.4/git.html[documentation for release 1.7.1.4] 85 86* release notes for 87 link:RelNotes/1.7.1.4.txt[1.7.1.4], 88 link:RelNotes/1.7.1.3.txt[1.7.1.3], 89 link:RelNotes/1.7.1.2.txt[1.7.1.2], 90 link:RelNotes/1.7.1.1.txt[1.7.1.1], 91 link:RelNotes/1.7.1.txt[1.7.1]. 92 93* link:v1.7.0.9/git.html[documentation for release 1.7.0.9] 94 95* release notes for 96 link:RelNotes/1.7.0.9.txt[1.7.0.9], 97 link:RelNotes/1.7.0.8.txt[1.7.0.8], 98 link:RelNotes/1.7.0.7.txt[1.7.0.7], 99 link:RelNotes/1.7.0.6.txt[1.7.0.6], 100 link:RelNotes/1.7.0.5.txt[1.7.0.5], 101 link:RelNotes/1.7.0.4.txt[1.7.0.4], 102 link:RelNotes/1.7.0.3.txt[1.7.0.3], 103 link:RelNotes/1.7.0.2.txt[1.7.0.2], 104 link:RelNotes/1.7.0.1.txt[1.7.0.1], 105 link:RelNotes/1.7.0.txt[1.7.0]. 106 107* link:v1.6.6.3/git.html[documentation for release 1.6.6.3] 108 109* release notes for 110 link:RelNotes/1.6.6.3.txt[1.6.6.3], 111 link:RelNotes/1.6.6.2.txt[1.6.6.2], 112 link:RelNotes/1.6.6.1.txt[1.6.6.1], 113 link:RelNotes/1.6.6.txt[1.6.6]. 114 115* link:v1.6.5.9/git.html[documentation for release 1.6.5.9] 116 117* release notes for 118 link:RelNotes/1.6.5.9.txt[1.6.5.9], 119 link:RelNotes/1.6.5.8.txt[1.6.5.8], 120 link:RelNotes/1.6.5.7.txt[1.6.5.7], 121 link:RelNotes/1.6.5.6.txt[1.6.5.6], 122 link:RelNotes/1.6.5.5.txt[1.6.5.5], 123 link:RelNotes/1.6.5.4.txt[1.6.5.4], 124 link:RelNotes/1.6.5.3.txt[1.6.5.3], 125 link:RelNotes/1.6.5.2.txt[1.6.5.2], 126 link:RelNotes/1.6.5.1.txt[1.6.5.1], 127 link:RelNotes/1.6.5.txt[1.6.5]. 128 129* link:v1.6.4.5/git.html[documentation for release 1.6.4.5] 130 131* release notes for 132 link:RelNotes/1.6.4.5.txt[1.6.4.5], 133 link:RelNotes/1.6.4.4.txt[1.6.4.4], 134 link:RelNotes/1.6.4.3.txt[1.6.4.3], 135 link:RelNotes/1.6.4.2.txt[1.6.4.2], 136 link:RelNotes/1.6.4.1.txt[1.6.4.1], 137 link:RelNotes/1.6.4.txt[1.6.4]. 138 139* link:v1.6.3.4/git.html[documentation for release 1.6.3.4] 140 141* release notes for 142 link:RelNotes/1.6.3.4.txt[1.6.3.4], 143 link:RelNotes/1.6.3.3.txt[1.6.3.3], 144 link:RelNotes/1.6.3.2.txt[1.6.3.2], 145 link:RelNotes/1.6.3.1.txt[1.6.3.1], 146 link:RelNotes/1.6.3.txt[1.6.3]. 147 148* release notes for 149 link:RelNotes/1.6.2.5.txt[1.6.2.5], 150 link:RelNotes/1.6.2.4.txt[1.6.2.4], 151 link:RelNotes/1.6.2.3.txt[1.6.2.3], 152 link:RelNotes/1.6.2.2.txt[1.6.2.2], 153 link:RelNotes/1.6.2.1.txt[1.6.2.1], 154 link:RelNotes/1.6.2.txt[1.6.2]. 155 156* link:v1.6.1.3/git.html[documentation for release 1.6.1.3] 157 158* release notes for 159 link:RelNotes/1.6.1.3.txt[1.6.1.3], 160 link:RelNotes/1.6.1.2.txt[1.6.1.2], 161 link:RelNotes/1.6.1.1.txt[1.6.1.1], 162 link:RelNotes/1.6.1.txt[1.6.1]. 163 164* link:v1.6.0.6/git.html[documentation for release 1.6.0.6] 165 166* release notes for 167 link:RelNotes/1.6.0.6.txt[1.6.0.6], 168 link:RelNotes/1.6.0.5.txt[1.6.0.5], 169 link:RelNotes/1.6.0.4.txt[1.6.0.4], 170 link:RelNotes/1.6.0.3.txt[1.6.0.3], 171 link:RelNotes/1.6.0.2.txt[1.6.0.2], 172 link:RelNotes/1.6.0.1.txt[1.6.0.1], 173 link:RelNotes/1.6.0.txt[1.6.0]. 174 175* link:v1.5.6.6/git.html[documentation for release 1.5.6.6] 176 177* release notes for 178 link:RelNotes/1.5.6.6.txt[1.5.6.6], 179 link:RelNotes/1.5.6.5.txt[1.5.6.5], 180 link:RelNotes/1.5.6.4.txt[1.5.6.4], 181 link:RelNotes/1.5.6.3.txt[1.5.6.3], 182 link:RelNotes/1.5.6.2.txt[1.5.6.2], 183 link:RelNotes/1.5.6.1.txt[1.5.6.1], 184 link:RelNotes/1.5.6.txt[1.5.6]. 185 186* link:v1.5.5.6/git.html[documentation for release 1.5.5.6] 187 188* release notes for 189 link:RelNotes/1.5.5.6.txt[1.5.5.6], 190 link:RelNotes/1.5.5.5.txt[1.5.5.5], 191 link:RelNotes/1.5.5.4.txt[1.5.5.4], 192 link:RelNotes/1.5.5.3.txt[1.5.5.3], 193 link:RelNotes/1.5.5.2.txt[1.5.5.2], 194 link:RelNotes/1.5.5.1.txt[1.5.5.1], 195 link:RelNotes/1.5.5.txt[1.5.5]. 196 197* link:v1.5.4.7/git.html[documentation for release 1.5.4.7] 198 199* release notes for 200 link:RelNotes/1.5.4.7.txt[1.5.4.7], 201 link:RelNotes/1.5.4.6.txt[1.5.4.6], 202 link:RelNotes/1.5.4.5.txt[1.5.4.5], 203 link:RelNotes/1.5.4.4.txt[1.5.4.4], 204 link:RelNotes/1.5.4.3.txt[1.5.4.3], 205 link:RelNotes/1.5.4.2.txt[1.5.4.2], 206 link:RelNotes/1.5.4.1.txt[1.5.4.1], 207 link:RelNotes/1.5.4.txt[1.5.4]. 208 209* link:v1.5.3.8/git.html[documentation for release 1.5.3.8] 210 211* release notes for 212 link:RelNotes/1.5.3.8.txt[1.5.3.8], 213 link:RelNotes/1.5.3.7.txt[1.5.3.7], 214 link:RelNotes/1.5.3.6.txt[1.5.3.6], 215 link:RelNotes/1.5.3.5.txt[1.5.3.5], 216 link:RelNotes/1.5.3.4.txt[1.5.3.4], 217 link:RelNotes/1.5.3.3.txt[1.5.3.3], 218 link:RelNotes/1.5.3.2.txt[1.5.3.2], 219 link:RelNotes/1.5.3.1.txt[1.5.3.1], 220 link:RelNotes/1.5.3.txt[1.5.3]. 221 222* link:v1.5.2.5/git.html[documentation for release 1.5.2.5] 223 224* release notes for 225 link:RelNotes/1.5.2.5.txt[1.5.2.5], 226 link:RelNotes/1.5.2.4.txt[1.5.2.4], 227 link:RelNotes/1.5.2.3.txt[1.5.2.3], 228 link:RelNotes/1.5.2.2.txt[1.5.2.2], 229 link:RelNotes/1.5.2.1.txt[1.5.2.1], 230 link:RelNotes/1.5.2.txt[1.5.2]. 231 232* link:v1.5.1.6/git.html[documentation for release 1.5.1.6] 233 234* release notes for 235 link:RelNotes/1.5.1.6.txt[1.5.1.6], 236 link:RelNotes/1.5.1.5.txt[1.5.1.5], 237 link:RelNotes/1.5.1.4.txt[1.5.1.4], 238 link:RelNotes/1.5.1.3.txt[1.5.1.3], 239 link:RelNotes/1.5.1.2.txt[1.5.1.2], 240 link:RelNotes/1.5.1.1.txt[1.5.1.1], 241 link:RelNotes/1.5.1.txt[1.5.1]. 242 243* link:v1.5.0.7/git.html[documentation for release 1.5.0.7] 244 245* release notes for 246 link:RelNotes/1.5.0.7.txt[1.5.0.7], 247 link:RelNotes/1.5.0.6.txt[1.5.0.6], 248 link:RelNotes/1.5.0.5.txt[1.5.0.5], 249 link:RelNotes/1.5.0.3.txt[1.5.0.3], 250 link:RelNotes/1.5.0.2.txt[1.5.0.2], 251 link:RelNotes/1.5.0.1.txt[1.5.0.1], 252 link:RelNotes/1.5.0.txt[1.5.0]. 253 254* documentation for release link:v1.4.4.4/git.html[1.4.4.4], 255 link:v1.3.3/git.html[1.3.3], 256 link:v1.2.6/git.html[1.2.6], 257 link:v1.0.13/git.html[1.0.13]. 258 259============ 260 261endif::stalenotes[] 262 263OPTIONS 264------- 265--version:: 266 Prints the git suite version that the 'git' program came from. 267 268--help:: 269 Prints the synopsis and a list of the most commonly used 270 commands. If the option '--all' or '-a' is given then all 271 available commands are printed. If a git command is named this 272 option will bring up the manual page for that command. 273+ 274Other options are available to control how the manual page is 275displayed. See linkgit:git-help[1] for more information, 276because `git --help ...` is converted internally into `git 277help ...`. 278 279-c <name>=<value>:: 280 Pass a configuration parameter to the command. The value 281 given will override values from configuration files. 282 The <name> is expected in the same format as listed by 283 'git config' (subkeys separated by dots). 284 285--exec-path[=<path>]:: 286 Path to wherever your core git programs are installed. 287 This can also be controlled by setting the GIT_EXEC_PATH 288 environment variable. If no path is given, 'git' will print 289 the current setting and then exit. 290 291--html-path:: 292 Print the path, without trailing slash, where git's HTML 293 documentation is installed and exit. 294 295--man-path:: 296 Print the manpath (see `man(1)`) for the man pages for 297 this version of git and exit. 298 299--info-path:: 300 Print the path where the Info files documenting this 301 version of git are installed and exit. 302 303-p:: 304--paginate:: 305 Pipe all output into 'less' (or if set, $PAGER) if standard 306 output is a terminal. This overrides the `pager.<cmd>` 307 configuration options (see the "Configuration Mechanism" section 308 below). 309 310--no-pager:: 311 Do not pipe git output into a pager. 312 313--git-dir=<path>:: 314 Set the path to the repository. This can also be controlled by 315 setting the GIT_DIR environment variable. It can be an absolute 316 path or relative path to current working directory. 317 318--work-tree=<path>:: 319 Set the path to the working tree. It can be an absolute path 320 or a path relative to the current working directory. 321 This can also be controlled by setting the GIT_WORK_TREE 322 environment variable and the core.worktree configuration 323 variable (see core.worktree in linkgit:git-config[1] for a 324 more detailed discussion). 325 326--bare:: 327 Treat the repository as a bare repository. If GIT_DIR 328 environment is not set, it is set to the current working 329 directory. 330 331--no-replace-objects:: 332 Do not use replacement refs to replace git objects. See 333 linkgit:git-replace[1] for more information. 334 335 336FURTHER DOCUMENTATION 337--------------------- 338 339See the references above to get started using git. The following is 340probably more detail than necessary for a first-time user. 341 342The link:user-manual.html#git-concepts[git concepts chapter of the 343user-manual] and linkgit:gitcore-tutorial[7] both provide 344introductions to the underlying git architecture. 345 346See linkgit:gitworkflows[7] for an overview of recommended workflows. 347 348See also the link:howto-index.html[howto] documents for some useful 349examples. 350 351The internals are documented in the 352link:technical/api-index.html[GIT API documentation]. 353 354GIT COMMANDS 355------------ 356 357We divide git into high level ("porcelain") commands and low level 358("plumbing") commands. 359 360High-level commands (porcelain) 361------------------------------- 362 363We separate the porcelain commands into the main commands and some 364ancillary user utilities. 365 366Main porcelain commands 367~~~~~~~~~~~~~~~~~~~~~~~ 368 369include::cmds-mainporcelain.txt[] 370 371Ancillary Commands 372~~~~~~~~~~~~~~~~~~ 373Manipulators: 374 375include::cmds-ancillarymanipulators.txt[] 376 377Interrogators: 378 379include::cmds-ancillaryinterrogators.txt[] 380 381 382Interacting with Others 383~~~~~~~~~~~~~~~~~~~~~~~ 384 385These commands are to interact with foreign SCM and with other 386people via patch over e-mail. 387 388include::cmds-foreignscminterface.txt[] 389 390 391Low-level commands (plumbing) 392----------------------------- 393 394Although git includes its 395own porcelain layer, its low-level commands are sufficient to support 396development of alternative porcelains. Developers of such porcelains 397might start by reading about linkgit:git-update-index[1] and 398linkgit:git-read-tree[1]. 399 400The interface (input, output, set of options and the semantics) 401to these low-level commands are meant to be a lot more stable 402than Porcelain level commands, because these commands are 403primarily for scripted use. The interface to Porcelain commands 404on the other hand are subject to change in order to improve the 405end user experience. 406 407The following description divides 408the low-level commands into commands that manipulate objects (in 409the repository, index, and working tree), commands that interrogate and 410compare objects, and commands that move objects and references between 411repositories. 412 413 414Manipulation commands 415~~~~~~~~~~~~~~~~~~~~~ 416 417include::cmds-plumbingmanipulators.txt[] 418 419 420Interrogation commands 421~~~~~~~~~~~~~~~~~~~~~~ 422 423include::cmds-plumbinginterrogators.txt[] 424 425In general, the interrogate commands do not touch the files in 426the working tree. 427 428 429Synching repositories 430~~~~~~~~~~~~~~~~~~~~~ 431 432include::cmds-synchingrepositories.txt[] 433 434The following are helper commands used by the above; end users 435typically do not use them directly. 436 437include::cmds-synchelpers.txt[] 438 439 440Internal helper commands 441~~~~~~~~~~~~~~~~~~~~~~~~ 442 443These are internal helper commands used by other commands; end 444users typically do not use them directly. 445 446include::cmds-purehelpers.txt[] 447 448 449Configuration Mechanism 450----------------------- 451 452Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file 453is used to hold per-repository configuration options. It is a 454simple text file modeled after `.ini` format familiar to some 455people. Here is an example: 456 457------------ 458# 459# A '#' or ';' character indicates a comment. 460# 461 462; core variables 463[core] 464 ; Don't trust file modes 465 filemode = false 466 467; user identity 468[user] 469 name = "Junio C Hamano" 470 email = "junkio@twinsun.com" 471 472------------ 473 474Various commands read from the configuration file and adjust 475their operation accordingly. See linkgit:git-config[1] for a 476list. 477 478 479Identifier Terminology 480---------------------- 481<object>:: 482 Indicates the object name for any type of object. 483 484<blob>:: 485 Indicates a blob object name. 486 487<tree>:: 488 Indicates a tree object name. 489 490<commit>:: 491 Indicates a commit object name. 492 493<tree-ish>:: 494 Indicates a tree, commit or tag object name. A 495 command that takes a <tree-ish> argument ultimately wants to 496 operate on a <tree> object but automatically dereferences 497 <commit> and <tag> objects that point at a <tree>. 498 499<commit-ish>:: 500 Indicates a commit or tag object name. A 501 command that takes a <commit-ish> argument ultimately wants to 502 operate on a <commit> object but automatically dereferences 503 <tag> objects that point at a <commit>. 504 505<type>:: 506 Indicates that an object type is required. 507 Currently one of: `blob`, `tree`, `commit`, or `tag`. 508 509<file>:: 510 Indicates a filename - almost always relative to the 511 root of the tree structure `GIT_INDEX_FILE` describes. 512 513Symbolic Identifiers 514-------------------- 515Any git command accepting any <object> can also use the following 516symbolic notation: 517 518HEAD:: 519 indicates the head of the current branch (i.e. the 520 contents of `$GIT_DIR/HEAD`). 521 522<tag>:: 523 a valid tag 'name' 524 (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`). 525 526<head>:: 527 a valid head 'name' 528 (i.e. the contents of `$GIT_DIR/refs/heads/<head>`). 529 530For a more complete list of ways to spell object names, see 531"SPECIFYING REVISIONS" section in linkgit:gitrevisions[7]. 532 533 534File/Directory Structure 535------------------------ 536 537Please see the linkgit:gitrepository-layout[5] document. 538 539Read linkgit:githooks[5] for more details about each hook. 540 541Higher level SCMs may provide and manage additional information in the 542`$GIT_DIR`. 543 544 545Terminology 546----------- 547Please see linkgit:gitglossary[7]. 548 549 550Environment Variables 551--------------------- 552Various git commands use the following environment variables: 553 554The git Repository 555~~~~~~~~~~~~~~~~~~ 556These environment variables apply to 'all' core git commands. Nb: it 557is worth noting that they may be used/overridden by SCMS sitting above 558git so take care if using Cogito etc. 559 560'GIT_INDEX_FILE':: 561 This environment allows the specification of an alternate 562 index file. If not specified, the default of `$GIT_DIR/index` 563 is used. 564 565'GIT_OBJECT_DIRECTORY':: 566 If the object storage directory is specified via this 567 environment variable then the sha1 directories are created 568 underneath - otherwise the default `$GIT_DIR/objects` 569 directory is used. 570 571'GIT_ALTERNATE_OBJECT_DIRECTORIES':: 572 Due to the immutable nature of git objects, old objects can be 573 archived into shared, read-only directories. This variable 574 specifies a ":" separated (on Windows ";" separated) list 575 of git object directories which can be used to search for git 576 objects. New objects will not be written to these directories. 577 578'GIT_DIR':: 579 If the 'GIT_DIR' environment variable is set then it 580 specifies a path to use instead of the default `.git` 581 for the base of the repository. 582 583'GIT_WORK_TREE':: 584 Set the path to the working tree. The value will not be 585 used in combination with repositories found automatically in 586 a .git directory (i.e. $GIT_DIR is not set). 587 This can also be controlled by the '--work-tree' command line 588 option and the core.worktree configuration variable. 589 590'GIT_CEILING_DIRECTORIES':: 591 This should be a colon-separated list of absolute paths. 592 If set, it is a list of directories that git should not chdir 593 up into while looking for a repository directory. 594 It will not exclude the current working directory or 595 a GIT_DIR set on the command line or in the environment. 596 (Useful for excluding slow-loading network directories.) 597 598'GIT_DISCOVERY_ACROSS_FILESYSTEM':: 599 When run in a directory that does not have ".git" repository 600 directory, git tries to find such a directory in the parent 601 directories to find the top of the working tree, but by default it 602 does not cross filesystem boundaries. This environment variable 603 can be set to true to tell git not to stop at filesystem 604 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect 605 an explicit repository directory set via 'GIT_DIR' or on the 606 command line. 607 608git Commits 609~~~~~~~~~~~ 610'GIT_AUTHOR_NAME':: 611'GIT_AUTHOR_EMAIL':: 612'GIT_AUTHOR_DATE':: 613'GIT_COMMITTER_NAME':: 614'GIT_COMMITTER_EMAIL':: 615'GIT_COMMITTER_DATE':: 616'EMAIL':: 617 see linkgit:git-commit-tree[1] 618 619git Diffs 620~~~~~~~~~ 621'GIT_DIFF_OPTS':: 622 Only valid setting is "--unified=??" or "-u??" to set the 623 number of context lines shown when a unified diff is created. 624 This takes precedence over any "-U" or "--unified" option 625 value passed on the git diff command line. 626 627'GIT_EXTERNAL_DIFF':: 628 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the 629 program named by it is called, instead of the diff invocation 630 described above. For a path that is added, removed, or modified, 631 'GIT_EXTERNAL_DIFF' is called with 7 parameters: 632 633 path old-file old-hex old-mode new-file new-hex new-mode 634+ 635where: 636 637 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the 638 contents of <old|new>, 639 <old|new>-hex:: are the 40-hexdigit SHA1 hashes, 640 <old|new>-mode:: are the octal representation of the file modes. 641+ 642The file parameters can point at the user's working file 643(e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file` 644when a new file is added), or a temporary file (e.g. `old-file` in the 645index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the 646temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits. 647+ 648For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1 649parameter, <path>. 650 651other 652~~~~~ 653'GIT_MERGE_VERBOSITY':: 654 A number controlling the amount of output shown by 655 the recursive merge strategy. Overrides merge.verbosity. 656 See linkgit:git-merge[1] 657 658'GIT_PAGER':: 659 This environment variable overrides `$PAGER`. If it is set 660 to an empty string or to the value "cat", git will not launch 661 a pager. See also the `core.pager` option in 662 linkgit:git-config[1]. 663 664'GIT_SSH':: 665 If this environment variable is set then 'git fetch' 666 and 'git push' will use this command instead 667 of 'ssh' when they need to connect to a remote system. 668 The '$GIT_SSH' command will be given exactly two arguments: 669 the 'username@host' (or just 'host') from the URL and the 670 shell command to execute on that remote system. 671+ 672To pass options to the program that you want to list in GIT_SSH 673you will need to wrap the program and options into a shell script, 674then set GIT_SSH to refer to the shell script. 675+ 676Usually it is easier to configure any desired options through your 677personal `.ssh/config` file. Please consult your ssh documentation 678for further details. 679 680'GIT_ASKPASS':: 681 If this environment variable is set, then git commands which need to 682 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication) 683 will call this program with a suitable prompt as command line argument 684 and read the password from its STDOUT. See also the 'core.askpass' 685 option in linkgit:git-config[1]. 686 687'GIT_FLUSH':: 688 If this environment variable is set to "1", then commands such 689 as 'git blame' (in incremental mode), 'git rev-list', 'git log', 690 and 'git whatchanged' will force a flush of the output stream 691 after each commit-oriented record have been flushed. If this 692 variable is set to "0", the output of these commands will be done 693 using completely buffered I/O. If this environment variable is 694 not set, git will choose buffered or record-oriented flushing 695 based on whether stdout appears to be redirected to a file or not. 696 697'GIT_TRACE':: 698 If this variable is set to "1", "2" or "true" (comparison 699 is case insensitive), git will print `trace:` messages on 700 stderr telling about alias expansion, built-in command 701 execution and external command execution. 702 If this variable is set to an integer value greater than 1 703 and lower than 10 (strictly) then git will interpret this 704 value as an open file descriptor and will try to write the 705 trace messages into this file descriptor. 706 Alternatively, if this variable is set to an absolute path 707 (starting with a '/' character), git will interpret this 708 as a file path and will try to write the trace messages 709 into it. 710 711Discussion[[Discussion]] 712------------------------ 713 714More detail on the following is available from the 715link:user-manual.html#git-concepts[git concepts chapter of the 716user-manual] and linkgit:gitcore-tutorial[7]. 717 718A git project normally consists of a working directory with a ".git" 719subdirectory at the top level. The .git directory contains, among other 720things, a compressed object database representing the complete history 721of the project, an "index" file which links that history to the current 722contents of the working tree, and named pointers into that history such 723as tags and branch heads. 724 725The object database contains objects of three main types: blobs, which 726hold file data; trees, which point to blobs and other trees to build up 727directory hierarchies; and commits, which each reference a single tree 728and some number of parent commits. 729 730The commit, equivalent to what other systems call a "changeset" or 731"version", represents a step in the project's history, and each parent 732represents an immediately preceding step. Commits with more than one 733parent represent merges of independent lines of development. 734 735All objects are named by the SHA1 hash of their contents, normally 736written as a string of 40 hex digits. Such names are globally unique. 737The entire history leading up to a commit can be vouched for by signing 738just that commit. A fourth object type, the tag, is provided for this 739purpose. 740 741When first created, objects are stored in individual files, but for 742efficiency may later be compressed together into "pack files". 743 744Named pointers called refs mark interesting points in history. A ref 745may contain the SHA1 name of an object or the name of another ref. Refs 746with names beginning `ref/head/` contain the SHA1 name of the most 747recent commit (or "head") of a branch under development. SHA1 names of 748tags of interest are stored under `ref/tags/`. A special ref named 749`HEAD` contains the name of the currently checked-out branch. 750 751The index file is initialized with a list of all paths and, for each 752path, a blob object and a set of attributes. The blob object represents 753the contents of the file as of the head of the current branch. The 754attributes (last modified time, size, etc.) are taken from the 755corresponding file in the working tree. Subsequent changes to the 756working tree can be found by comparing these attributes. The index may 757be updated with new content, and new commits may be created from the 758content stored in the index. 759 760The index is also capable of storing multiple entries (called "stages") 761for a given pathname. These stages are used to hold the various 762unmerged version of a file when a merge is in progress. 763 764Authors 765------- 766Git was started by Linus Torvalds, and is currently maintained by Junio 767C Hamano. Numerous contributions have come from the git mailing list 768<git@vger.kernel.org>. For a more complete list of contributors, see 769http://git-scm.com/about. If you have a clone of git.git itself, the 770output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you 771the authors for specific parts of the project. 772 773Reporting Bugs 774-------------- 775 776Report bugs to the Git mailing list <git@vger.kernel.org> where the 777development and maintenance is primarily done. You do not have to be 778subscribed to the list to send a message there. 779 780SEE ALSO 781-------- 782linkgit:gittutorial[7], linkgit:gittutorial-2[7], 783link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7], 784linkgit:gitglossary[7], linkgit:gitcore-tutorial[7], 785linkgit:gitcli[7], link:user-manual.html[The Git User's Manual], 786linkgit:gitworkflows[7] 787 788GIT 789--- 790Part of the linkgit:git[1] suite