Documentation/git.txt

   1 git(1)
   2 ======
   3
   4 NAME
   5 ----
   6 git - the stupid content tracker
   7
   8
   9 SYNOPSIS
  10 --------
  11 [verse]
  12 'git' [--version] [--help] [-C <path>] [-c <name>=<value>]
  13     [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
  14     [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
  15     [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
  16     <command> [<args>]
  17
  18 DESCRIPTION
  19 -----------
  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.
  23
  24 See linkgit:gittutorial[7] to get started, then see
  25 linkgit:giteveryday[7] for a useful minimum set of
  26 commands.  The link:user-manual.html[Git User's Manual] has a more
  27 in-depth introduction.
  28
  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.
  33
  34 A formatted and hyperlinked copy of the latest Git documentation
  35 can be viewed at `https://git.github.io/htmldocs/git.html`.
  36
  37 ifdef::stalenotes[]
  38 [NOTE]
  39 ============
  40
  41 You are reading the documentation for the latest (possibly
  42 unreleased) version of Git, that is available from the 'master'
  43 branch of the `git.git` repository.
  44 Documentation for older releases are available here:
  45
  46 * link:v2.9.3/git.html[documentation for release 2.9.3]
  47
  48 * release notes for
  49   link:RelNotes/2.9.3.txt[2.9.3],
  50   link:RelNotes/2.9.2.txt[2.9.2],
  51   link:RelNotes/2.9.1.txt[2.9.1],
  52   link:RelNotes/2.9.0.txt[2.9].
  53
  54 * link:v2.8.4/git.html[documentation for release 2.8.4]
  55
  56 * release notes for
  57   link:RelNotes/2.8.4.txt[2.8.4],
  58   link:RelNotes/2.8.3.txt[2.8.3],
  59   link:RelNotes/2.8.2.txt[2.8.2],
  60   link:RelNotes/2.8.1.txt[2.8.1],
  61   link:RelNotes/2.8.0.txt[2.8].
  62
  63 * link:v2.7.3/git.html[documentation for release 2.7.3]
  64
  65 * release notes for
  66   link:RelNotes/2.7.3.txt[2.7.3],
  67   link:RelNotes/2.7.2.txt[2.7.2],
  68   link:RelNotes/2.7.1.txt[2.7.1],
  69   link:RelNotes/2.7.0.txt[2.7].
  70
  71 * link:v2.6.6/git.html[documentation for release 2.6.6]
  72
  73 * release notes for
  74   link:RelNotes/2.6.6.txt[2.6.6],
  75   link:RelNotes/2.6.5.txt[2.6.5],
  76   link:RelNotes/2.6.4.txt[2.6.4],
  77   link:RelNotes/2.6.3.txt[2.6.3],
  78   link:RelNotes/2.6.2.txt[2.6.2],
  79   link:RelNotes/2.6.1.txt[2.6.1],
  80   link:RelNotes/2.6.0.txt[2.6].
  81
  82 * link:v2.5.5/git.html[documentation for release 2.5.5]
  83
  84 * release notes for
  85   link:RelNotes/2.5.5.txt[2.5.5],
  86   link:RelNotes/2.5.4.txt[2.5.4],
  87   link:RelNotes/2.5.3.txt[2.5.3],
  88   link:RelNotes/2.5.2.txt[2.5.2],
  89   link:RelNotes/2.5.1.txt[2.5.1],
  90   link:RelNotes/2.5.0.txt[2.5].
  91
  92 * link:v2.4.11/git.html[documentation for release 2.4.11]
  93
  94 * release notes for
  95   link:RelNotes/2.4.11.txt[2.4.11],
  96   link:RelNotes/2.4.10.txt[2.4.10],
  97   link:RelNotes/2.4.9.txt[2.4.9],
  98   link:RelNotes/2.4.8.txt[2.4.8],
  99   link:RelNotes/2.4.7.txt[2.4.7],
 100   link:RelNotes/2.4.6.txt[2.4.6],
 101   link:RelNotes/2.4.5.txt[2.4.5],
 102   link:RelNotes/2.4.4.txt[2.4.4],
 103   link:RelNotes/2.4.3.txt[2.4.3],
 104   link:RelNotes/2.4.2.txt[2.4.2],
 105   link:RelNotes/2.4.1.txt[2.4.1],
 106   link:RelNotes/2.4.0.txt[2.4].
 107
 108 * link:v2.3.10/git.html[documentation for release 2.3.10]
 109
 110 * release notes for
 111   link:RelNotes/2.3.10.txt[2.3.10],
 112   link:RelNotes/2.3.9.txt[2.3.9],
 113   link:RelNotes/2.3.8.txt[2.3.8],
 114   link:RelNotes/2.3.7.txt[2.3.7],
 115   link:RelNotes/2.3.6.txt[2.3.6],
 116   link:RelNotes/2.3.5.txt[2.3.5],
 117   link:RelNotes/2.3.4.txt[2.3.4],
 118   link:RelNotes/2.3.3.txt[2.3.3],
 119   link:RelNotes/2.3.2.txt[2.3.2],
 120   link:RelNotes/2.3.1.txt[2.3.1],
 121   link:RelNotes/2.3.0.txt[2.3].
 122
 123 * link:v2.2.3/git.html[documentation for release 2.2.3]
 124
 125 * release notes for
 126   link:RelNotes/2.2.3.txt[2.2.3],
 127   link:RelNotes/2.2.2.txt[2.2.2],
 128   link:RelNotes/2.2.1.txt[2.2.1],
 129   link:RelNotes/2.2.0.txt[2.2].
 130
 131 * link:v2.1.4/git.html[documentation for release 2.1.4]
 132
 133 * release notes for
 134   link:RelNotes/2.1.4.txt[2.1.4],
 135   link:RelNotes/2.1.3.txt[2.1.3],
 136   link:RelNotes/2.1.2.txt[2.1.2],
 137   link:RelNotes/2.1.1.txt[2.1.1],
 138   link:RelNotes/2.1.0.txt[2.1].
 139
 140 * link:v2.0.5/git.html[documentation for release 2.0.5]
 141
 142 * release notes for
 143   link:RelNotes/2.0.5.txt[2.0.5],
 144   link:RelNotes/2.0.4.txt[2.0.4],
 145   link:RelNotes/2.0.3.txt[2.0.3],
 146   link:RelNotes/2.0.2.txt[2.0.2],
 147   link:RelNotes/2.0.1.txt[2.0.1],
 148   link:RelNotes/2.0.0.txt[2.0.0].
 149
 150 * link:v1.9.5/git.html[documentation for release 1.9.5]
 151
 152 * release notes for
 153   link:RelNotes/1.9.5.txt[1.9.5],
 154   link:RelNotes/1.9.4.txt[1.9.4],
 155   link:RelNotes/1.9.3.txt[1.9.3],
 156   link:RelNotes/1.9.2.txt[1.9.2],
 157   link:RelNotes/1.9.1.txt[1.9.1],
 158   link:RelNotes/1.9.0.txt[1.9.0].
 159
 160 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
 161
 162 * release notes for
 163   link:RelNotes/1.8.5.6.txt[1.8.5.6],
 164   link:RelNotes/1.8.5.5.txt[1.8.5.5],
 165   link:RelNotes/1.8.5.4.txt[1.8.5.4],
 166   link:RelNotes/1.8.5.3.txt[1.8.5.3],
 167   link:RelNotes/1.8.5.2.txt[1.8.5.2],
 168   link:RelNotes/1.8.5.1.txt[1.8.5.1],
 169   link:RelNotes/1.8.5.txt[1.8.5].
 170
 171 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
 172
 173 * release notes for
 174   link:RelNotes/1.8.4.5.txt[1.8.4.5],
 175   link:RelNotes/1.8.4.4.txt[1.8.4.4],
 176   link:RelNotes/1.8.4.3.txt[1.8.4.3],
 177   link:RelNotes/1.8.4.2.txt[1.8.4.2],
 178   link:RelNotes/1.8.4.1.txt[1.8.4.1],
 179   link:RelNotes/1.8.4.txt[1.8.4].
 180
 181 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
 182
 183 * release notes for
 184   link:RelNotes/1.8.3.4.txt[1.8.3.4],
 185   link:RelNotes/1.8.3.3.txt[1.8.3.3],
 186   link:RelNotes/1.8.3.2.txt[1.8.3.2],
 187   link:RelNotes/1.8.3.1.txt[1.8.3.1],
 188   link:RelNotes/1.8.3.txt[1.8.3].
 189
 190 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
 191
 192 * release notes for
 193   link:RelNotes/1.8.2.3.txt[1.8.2.3],
 194   link:RelNotes/1.8.2.2.txt[1.8.2.2],
 195   link:RelNotes/1.8.2.1.txt[1.8.2.1],
 196   link:RelNotes/1.8.2.txt[1.8.2].
 197
 198 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
 199
 200 * release notes for
 201   link:RelNotes/1.8.1.6.txt[1.8.1.6],
 202   link:RelNotes/1.8.1.5.txt[1.8.1.5],
 203   link:RelNotes/1.8.1.4.txt[1.8.1.4],
 204   link:RelNotes/1.8.1.3.txt[1.8.1.3],
 205   link:RelNotes/1.8.1.2.txt[1.8.1.2],
 206   link:RelNotes/1.8.1.1.txt[1.8.1.1],
 207   link:RelNotes/1.8.1.txt[1.8.1].
 208
 209 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
 210
 211 * release notes for
 212   link:RelNotes/1.8.0.3.txt[1.8.0.3],
 213   link:RelNotes/1.8.0.2.txt[1.8.0.2],
 214   link:RelNotes/1.8.0.1.txt[1.8.0.1],
 215   link:RelNotes/1.8.0.txt[1.8.0].
 216
 217 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
 218
 219 * release notes for
 220   link:RelNotes/1.7.12.4.txt[1.7.12.4],
 221   link:RelNotes/1.7.12.3.txt[1.7.12.3],
 222   link:RelNotes/1.7.12.2.txt[1.7.12.2],
 223   link:RelNotes/1.7.12.1.txt[1.7.12.1],
 224   link:RelNotes/1.7.12.txt[1.7.12].
 225
 226 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
 227
 228 * release notes for
 229   link:RelNotes/1.7.11.7.txt[1.7.11.7],
 230   link:RelNotes/1.7.11.6.txt[1.7.11.6],
 231   link:RelNotes/1.7.11.5.txt[1.7.11.5],
 232   link:RelNotes/1.7.11.4.txt[1.7.11.4],
 233   link:RelNotes/1.7.11.3.txt[1.7.11.3],
 234   link:RelNotes/1.7.11.2.txt[1.7.11.2],
 235   link:RelNotes/1.7.11.1.txt[1.7.11.1],
 236   link:RelNotes/1.7.11.txt[1.7.11].
 237
 238 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
 239
 240 * release notes for
 241   link:RelNotes/1.7.10.5.txt[1.7.10.5],
 242   link:RelNotes/1.7.10.4.txt[1.7.10.4],
 243   link:RelNotes/1.7.10.3.txt[1.7.10.3],
 244   link:RelNotes/1.7.10.2.txt[1.7.10.2],
 245   link:RelNotes/1.7.10.1.txt[1.7.10.1],
 246   link:RelNotes/1.7.10.txt[1.7.10].
 247
 248 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
 249
 250 * release notes for
 251   link:RelNotes/1.7.9.7.txt[1.7.9.7],
 252   link:RelNotes/1.7.9.6.txt[1.7.9.6],
 253   link:RelNotes/1.7.9.5.txt[1.7.9.5],
 254   link:RelNotes/1.7.9.4.txt[1.7.9.4],
 255   link:RelNotes/1.7.9.3.txt[1.7.9.3],
 256   link:RelNotes/1.7.9.2.txt[1.7.9.2],
 257   link:RelNotes/1.7.9.1.txt[1.7.9.1],
 258   link:RelNotes/1.7.9.txt[1.7.9].
 259
 260 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
 261
 262 * release notes for
 263   link:RelNotes/1.7.8.6.txt[1.7.8.6],
 264   link:RelNotes/1.7.8.5.txt[1.7.8.5],
 265   link:RelNotes/1.7.8.4.txt[1.7.8.4],
 266   link:RelNotes/1.7.8.3.txt[1.7.8.3],
 267   link:RelNotes/1.7.8.2.txt[1.7.8.2],
 268   link:RelNotes/1.7.8.1.txt[1.7.8.1],
 269   link:RelNotes/1.7.8.txt[1.7.8].
 270
 271 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
 272
 273 * release notes for
 274   link:RelNotes/1.7.7.7.txt[1.7.7.7],
 275   link:RelNotes/1.7.7.6.txt[1.7.7.6],
 276   link:RelNotes/1.7.7.5.txt[1.7.7.5],
 277   link:RelNotes/1.7.7.4.txt[1.7.7.4],
 278   link:RelNotes/1.7.7.3.txt[1.7.7.3],
 279   link:RelNotes/1.7.7.2.txt[1.7.7.2],
 280   link:RelNotes/1.7.7.1.txt[1.7.7.1],
 281   link:RelNotes/1.7.7.txt[1.7.7].
 282
 283 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
 284
 285 * release notes for
 286   link:RelNotes/1.7.6.6.txt[1.7.6.6],
 287   link:RelNotes/1.7.6.5.txt[1.7.6.5],
 288   link:RelNotes/1.7.6.4.txt[1.7.6.4],
 289   link:RelNotes/1.7.6.3.txt[1.7.6.3],
 290   link:RelNotes/1.7.6.2.txt[1.7.6.2],
 291   link:RelNotes/1.7.6.1.txt[1.7.6.1],
 292   link:RelNotes/1.7.6.txt[1.7.6].
 293
 294 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
 295
 296 * release notes for
 297   link:RelNotes/1.7.5.4.txt[1.7.5.4],
 298   link:RelNotes/1.7.5.3.txt[1.7.5.3],
 299   link:RelNotes/1.7.5.2.txt[1.7.5.2],
 300   link:RelNotes/1.7.5.1.txt[1.7.5.1],
 301   link:RelNotes/1.7.5.txt[1.7.5].
 302
 303 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
 304
 305 * release notes for
 306   link:RelNotes/1.7.4.5.txt[1.7.4.5],
 307   link:RelNotes/1.7.4.4.txt[1.7.4.4],
 308   link:RelNotes/1.7.4.3.txt[1.7.4.3],
 309   link:RelNotes/1.7.4.2.txt[1.7.4.2],
 310   link:RelNotes/1.7.4.1.txt[1.7.4.1],
 311   link:RelNotes/1.7.4.txt[1.7.4].
 312
 313 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
 314
 315 * release notes for
 316   link:RelNotes/1.7.3.5.txt[1.7.3.5],
 317   link:RelNotes/1.7.3.4.txt[1.7.3.4],
 318   link:RelNotes/1.7.3.3.txt[1.7.3.3],
 319   link:RelNotes/1.7.3.2.txt[1.7.3.2],
 320   link:RelNotes/1.7.3.1.txt[1.7.3.1],
 321   link:RelNotes/1.7.3.txt[1.7.3].
 322
 323 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
 324
 325 * release notes for
 326   link:RelNotes/1.7.2.5.txt[1.7.2.5],
 327   link:RelNotes/1.7.2.4.txt[1.7.2.4],
 328   link:RelNotes/1.7.2.3.txt[1.7.2.3],
 329   link:RelNotes/1.7.2.2.txt[1.7.2.2],
 330   link:RelNotes/1.7.2.1.txt[1.7.2.1],
 331   link:RelNotes/1.7.2.txt[1.7.2].
 332
 333 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
 334
 335 * release notes for
 336   link:RelNotes/1.7.1.4.txt[1.7.1.4],
 337   link:RelNotes/1.7.1.3.txt[1.7.1.3],
 338   link:RelNotes/1.7.1.2.txt[1.7.1.2],
 339   link:RelNotes/1.7.1.1.txt[1.7.1.1],
 340   link:RelNotes/1.7.1.txt[1.7.1].
 341
 342 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
 343
 344 * release notes for
 345   link:RelNotes/1.7.0.9.txt[1.7.0.9],
 346   link:RelNotes/1.7.0.8.txt[1.7.0.8],
 347   link:RelNotes/1.7.0.7.txt[1.7.0.7],
 348   link:RelNotes/1.7.0.6.txt[1.7.0.6],
 349   link:RelNotes/1.7.0.5.txt[1.7.0.5],
 350   link:RelNotes/1.7.0.4.txt[1.7.0.4],
 351   link:RelNotes/1.7.0.3.txt[1.7.0.3],
 352   link:RelNotes/1.7.0.2.txt[1.7.0.2],
 353   link:RelNotes/1.7.0.1.txt[1.7.0.1],
 354   link:RelNotes/1.7.0.txt[1.7.0].
 355
 356 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
 357
 358 * release notes for
 359   link:RelNotes/1.6.6.3.txt[1.6.6.3],
 360   link:RelNotes/1.6.6.2.txt[1.6.6.2],
 361   link:RelNotes/1.6.6.1.txt[1.6.6.1],
 362   link:RelNotes/1.6.6.txt[1.6.6].
 363
 364 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
 365
 366 * release notes for
 367   link:RelNotes/1.6.5.9.txt[1.6.5.9],
 368   link:RelNotes/1.6.5.8.txt[1.6.5.8],
 369   link:RelNotes/1.6.5.7.txt[1.6.5.7],
 370   link:RelNotes/1.6.5.6.txt[1.6.5.6],
 371   link:RelNotes/1.6.5.5.txt[1.6.5.5],
 372   link:RelNotes/1.6.5.4.txt[1.6.5.4],
 373   link:RelNotes/1.6.5.3.txt[1.6.5.3],
 374   link:RelNotes/1.6.5.2.txt[1.6.5.2],
 375   link:RelNotes/1.6.5.1.txt[1.6.5.1],
 376   link:RelNotes/1.6.5.txt[1.6.5].
 377
 378 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
 379
 380 * release notes for
 381   link:RelNotes/1.6.4.5.txt[1.6.4.5],
 382   link:RelNotes/1.6.4.4.txt[1.6.4.4],
 383   link:RelNotes/1.6.4.3.txt[1.6.4.3],
 384   link:RelNotes/1.6.4.2.txt[1.6.4.2],
 385   link:RelNotes/1.6.4.1.txt[1.6.4.1],
 386   link:RelNotes/1.6.4.txt[1.6.4].
 387
 388 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
 389
 390 * release notes for
 391   link:RelNotes/1.6.3.4.txt[1.6.3.4],
 392   link:RelNotes/1.6.3.3.txt[1.6.3.3],
 393   link:RelNotes/1.6.3.2.txt[1.6.3.2],
 394   link:RelNotes/1.6.3.1.txt[1.6.3.1],
 395   link:RelNotes/1.6.3.txt[1.6.3].
 396
 397 * release notes for
 398   link:RelNotes/1.6.2.5.txt[1.6.2.5],
 399   link:RelNotes/1.6.2.4.txt[1.6.2.4],
 400   link:RelNotes/1.6.2.3.txt[1.6.2.3],
 401   link:RelNotes/1.6.2.2.txt[1.6.2.2],
 402   link:RelNotes/1.6.2.1.txt[1.6.2.1],
 403   link:RelNotes/1.6.2.txt[1.6.2].
 404
 405 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
 406
 407 * release notes for
 408   link:RelNotes/1.6.1.3.txt[1.6.1.3],
 409   link:RelNotes/1.6.1.2.txt[1.6.1.2],
 410   link:RelNotes/1.6.1.1.txt[1.6.1.1],
 411   link:RelNotes/1.6.1.txt[1.6.1].
 412
 413 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
 414
 415 * release notes for
 416   link:RelNotes/1.6.0.6.txt[1.6.0.6],
 417   link:RelNotes/1.6.0.5.txt[1.6.0.5],
 418   link:RelNotes/1.6.0.4.txt[1.6.0.4],
 419   link:RelNotes/1.6.0.3.txt[1.6.0.3],
 420   link:RelNotes/1.6.0.2.txt[1.6.0.2],
 421   link:RelNotes/1.6.0.1.txt[1.6.0.1],
 422   link:RelNotes/1.6.0.txt[1.6.0].
 423
 424 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
 425
 426 * release notes for
 427   link:RelNotes/1.5.6.6.txt[1.5.6.6],
 428   link:RelNotes/1.5.6.5.txt[1.5.6.5],
 429   link:RelNotes/1.5.6.4.txt[1.5.6.4],
 430   link:RelNotes/1.5.6.3.txt[1.5.6.3],
 431   link:RelNotes/1.5.6.2.txt[1.5.6.2],
 432   link:RelNotes/1.5.6.1.txt[1.5.6.1],
 433   link:RelNotes/1.5.6.txt[1.5.6].
 434
 435 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
 436
 437 * release notes for
 438   link:RelNotes/1.5.5.6.txt[1.5.5.6],
 439   link:RelNotes/1.5.5.5.txt[1.5.5.5],
 440   link:RelNotes/1.5.5.4.txt[1.5.5.4],
 441   link:RelNotes/1.5.5.3.txt[1.5.5.3],
 442   link:RelNotes/1.5.5.2.txt[1.5.5.2],
 443   link:RelNotes/1.5.5.1.txt[1.5.5.1],
 444   link:RelNotes/1.5.5.txt[1.5.5].
 445
 446 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
 447
 448 * release notes for
 449   link:RelNotes/1.5.4.7.txt[1.5.4.7],
 450   link:RelNotes/1.5.4.6.txt[1.5.4.6],
 451   link:RelNotes/1.5.4.5.txt[1.5.4.5],
 452   link:RelNotes/1.5.4.4.txt[1.5.4.4],
 453   link:RelNotes/1.5.4.3.txt[1.5.4.3],
 454   link:RelNotes/1.5.4.2.txt[1.5.4.2],
 455   link:RelNotes/1.5.4.1.txt[1.5.4.1],
 456   link:RelNotes/1.5.4.txt[1.5.4].
 457
 458 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
 459
 460 * release notes for
 461   link:RelNotes/1.5.3.8.txt[1.5.3.8],
 462   link:RelNotes/1.5.3.7.txt[1.5.3.7],
 463   link:RelNotes/1.5.3.6.txt[1.5.3.6],
 464   link:RelNotes/1.5.3.5.txt[1.5.3.5],
 465   link:RelNotes/1.5.3.4.txt[1.5.3.4],
 466   link:RelNotes/1.5.3.3.txt[1.5.3.3],
 467   link:RelNotes/1.5.3.2.txt[1.5.3.2],
 468   link:RelNotes/1.5.3.1.txt[1.5.3.1],
 469   link:RelNotes/1.5.3.txt[1.5.3].
 470
 471 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
 472
 473 * release notes for
 474   link:RelNotes/1.5.2.5.txt[1.5.2.5],
 475   link:RelNotes/1.5.2.4.txt[1.5.2.4],
 476   link:RelNotes/1.5.2.3.txt[1.5.2.3],
 477   link:RelNotes/1.5.2.2.txt[1.5.2.2],
 478   link:RelNotes/1.5.2.1.txt[1.5.2.1],
 479   link:RelNotes/1.5.2.txt[1.5.2].
 480
 481 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
 482
 483 * release notes for
 484   link:RelNotes/1.5.1.6.txt[1.5.1.6],
 485   link:RelNotes/1.5.1.5.txt[1.5.1.5],
 486   link:RelNotes/1.5.1.4.txt[1.5.1.4],
 487   link:RelNotes/1.5.1.3.txt[1.5.1.3],
 488   link:RelNotes/1.5.1.2.txt[1.5.1.2],
 489   link:RelNotes/1.5.1.1.txt[1.5.1.1],
 490   link:RelNotes/1.5.1.txt[1.5.1].
 491
 492 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
 493
 494 * release notes for
 495   link:RelNotes/1.5.0.7.txt[1.5.0.7],
 496   link:RelNotes/1.5.0.6.txt[1.5.0.6],
 497   link:RelNotes/1.5.0.5.txt[1.5.0.5],
 498   link:RelNotes/1.5.0.3.txt[1.5.0.3],
 499   link:RelNotes/1.5.0.2.txt[1.5.0.2],
 500   link:RelNotes/1.5.0.1.txt[1.5.0.1],
 501   link:RelNotes/1.5.0.txt[1.5.0].
 502
 503 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
 504   link:v1.3.3/git.html[1.3.3],
 505   link:v1.2.6/git.html[1.2.6],
 506   link:v1.0.13/git.html[1.0.13].
 507
 508 ============
 509
 510 endif::stalenotes[]
 511
 512 OPTIONS
 513 -------
 514 --version::
 515         Prints the Git suite version that the 'git' program came from.
 516
 517 --help::
 518         Prints the synopsis and a list of the most commonly used
 519         commands. If the option `--all` or `-a` is given then all
 520         available commands are printed. If a Git command is named this
 521         option will bring up the manual page for that command.
 522 +
 523 Other options are available to control how the manual page is
 524 displayed. See linkgit:git-help[1] for more information,
 525 because `git --help ...` is converted internally into `git
 526 help ...`.
 527
 528 -C <path>::
 529         Run as if git was started in '<path>' instead of the current working
 530         directory.  When multiple `-C` options are given, each subsequent
 531         non-absolute `-C <path>` is interpreted relative to the preceding `-C
 532         <path>`.
 533 +
 534 This option affects options that expect path name like `--git-dir` and
 535 `--work-tree` in that their interpretations of the path names would be
 536 made relative to the working directory caused by the `-C` option. For
 537 example the following invocations are equivalent:
 538
 539     git --git-dir=a.git --work-tree=b -C c status
 540     git --git-dir=c/a.git --work-tree=c/b status
 541
 542 -c <name>=<value>::
 543         Pass a configuration parameter to the command. The value
 544         given will override values from configuration files.
 545         The <name> is expected in the same format as listed by
 546         'git config' (subkeys separated by dots).
 547 +
 548 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
 549 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
 550 config file). Including the equals but with an empty value (like `git -c
 551 foo.bar= ...`) sets `foo.bar` to the empty string.
 552
 553 --exec-path[=<path>]::
 554         Path to wherever your core Git programs are installed.
 555         This can also be controlled by setting the GIT_EXEC_PATH
 556         environment variable. If no path is given, 'git' will print
 557         the current setting and then exit.
 558
 559 --html-path::
 560         Print the path, without trailing slash, where Git's HTML
 561         documentation is installed and exit.
 562
 563 --man-path::
 564         Print the manpath (see `man(1)`) for the man pages for
 565         this version of Git and exit.
 566
 567 --info-path::
 568         Print the path where the Info files documenting this
 569         version of Git are installed and exit.
 570
 571 -p::
 572 --paginate::
 573         Pipe all output into 'less' (or if set, $PAGER) if standard
 574         output is a terminal.  This overrides the `pager.<cmd>`
 575         configuration options (see the "Configuration Mechanism" section
 576         below).
 577
 578 --no-pager::
 579         Do not pipe Git output into a pager.
 580
 581 --git-dir=<path>::
 582         Set the path to the repository. This can also be controlled by
 583         setting the `GIT_DIR` environment variable. It can be an absolute
 584         path or relative path to current working directory.
 585
 586 --work-tree=<path>::
 587         Set the path to the working tree. It can be an absolute path
 588         or a path relative to the current working directory.
 589         This can also be controlled by setting the GIT_WORK_TREE
 590         environment variable and the core.worktree configuration
 591         variable (see core.worktree in linkgit:git-config[1] for a
 592         more detailed discussion).
 593
 594 --namespace=<path>::
 595         Set the Git namespace.  See linkgit:gitnamespaces[7] for more
 596         details.  Equivalent to setting the `GIT_NAMESPACE` environment
 597         variable.
 598
 599 --bare::
 600         Treat the repository as a bare repository.  If GIT_DIR
 601         environment is not set, it is set to the current working
 602         directory.
 603
 604 --no-replace-objects::
 605         Do not use replacement refs to replace Git objects. See
 606         linkgit:git-replace[1] for more information.
 607
 608 --literal-pathspecs::
 609         Treat pathspecs literally (i.e. no globbing, no pathspec magic).
 610         This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
 611         variable to `1`.
 612
 613 --glob-pathspecs::
 614         Add "glob" magic to all pathspec. This is equivalent to setting
 615         the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
 616         globbing on individual pathspecs can be done using pathspec
 617         magic ":(literal)"
 618
 619 --noglob-pathspecs::
 620         Add "literal" magic to all pathspec. This is equivalent to setting
 621         the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
 622         globbing on individual pathspecs can be done using pathspec
 623         magic ":(glob)"
 624
 625 --icase-pathspecs::
 626         Add "icase" magic to all pathspec. This is equivalent to setting
 627         the `GIT_ICASE_PATHSPECS` environment variable to `1`.
 628
 629 GIT COMMANDS
 630 ------------
 631
 632 We divide Git into high level ("porcelain") commands and low level
 633 ("plumbing") commands.
 634
 635 High-level commands (porcelain)
 636 -------------------------------
 637
 638 We separate the porcelain commands into the main commands and some
 639 ancillary user utilities.
 640
 641 Main porcelain commands
 642 ~~~~~~~~~~~~~~~~~~~~~~~
 643
 644 include::cmds-mainporcelain.txt[]
 645
 646 Ancillary Commands
 647 ~~~~~~~~~~~~~~~~~~
 648 Manipulators:
 649
 650 include::cmds-ancillarymanipulators.txt[]
 651
 652 Interrogators:
 653
 654 include::cmds-ancillaryinterrogators.txt[]
 655
 656
 657 Interacting with Others
 658 ~~~~~~~~~~~~~~~~~~~~~~~
 659
 660 These commands are to interact with foreign SCM and with other
 661 people via patch over e-mail.
 662
 663 include::cmds-foreignscminterface.txt[]
 664
 665
 666 Low-level commands (plumbing)
 667 -----------------------------
 668
 669 Although Git includes its
 670 own porcelain layer, its low-level commands are sufficient to support
 671 development of alternative porcelains.  Developers of such porcelains
 672 might start by reading about linkgit:git-update-index[1] and
 673 linkgit:git-read-tree[1].
 674
 675 The interface (input, output, set of options and the semantics)
 676 to these low-level commands are meant to be a lot more stable
 677 than Porcelain level commands, because these commands are
 678 primarily for scripted use.  The interface to Porcelain commands
 679 on the other hand are subject to change in order to improve the
 680 end user experience.
 681
 682 The following description divides
 683 the low-level commands into commands that manipulate objects (in
 684 the repository, index, and working tree), commands that interrogate and
 685 compare objects, and commands that move objects and references between
 686 repositories.
 687
 688
 689 Manipulation commands
 690 ~~~~~~~~~~~~~~~~~~~~~
 691
 692 include::cmds-plumbingmanipulators.txt[]
 693
 694
 695 Interrogation commands
 696 ~~~~~~~~~~~~~~~~~~~~~~
 697
 698 include::cmds-plumbinginterrogators.txt[]
 699
 700 In general, the interrogate commands do not touch the files in
 701 the working tree.
 702
 703
 704 Synching repositories
 705 ~~~~~~~~~~~~~~~~~~~~~
 706
 707 include::cmds-synchingrepositories.txt[]
 708
 709 The following are helper commands used by the above; end users
 710 typically do not use them directly.
 711
 712 include::cmds-synchelpers.txt[]
 713
 714
 715 Internal helper commands
 716 ~~~~~~~~~~~~~~~~~~~~~~~~
 717
 718 These are internal helper commands used by other commands; end
 719 users typically do not use them directly.
 720
 721 include::cmds-purehelpers.txt[]
 722
 723
 724 Configuration Mechanism
 725 -----------------------
 726
 727 Git uses a simple text format to store customizations that are per
 728 repository and are per user.  Such a configuration file may look
 729 like this:
 730
 731 ------------
 732 #
 733 # A '#' or ';' character indicates a comment.
 734 #
 735
 736 ; core variables
 737 [core]
 738         ; Don't trust file modes
 739         filemode = false
 740
 741 ; user identity
 742 [user]
 743         name = "Junio C Hamano"
 744         email = "gitster@pobox.com"
 745
 746 ------------
 747
 748 Various commands read from the configuration file and adjust
 749 their operation accordingly.  See linkgit:git-config[1] for a
 750 list and more details about the configuration mechanism.
 751
 752
 753 Identifier Terminology
 754 ----------------------
 755 <object>::
 756         Indicates the object name for any type of object.
 757
 758 <blob>::
 759         Indicates a blob object name.
 760
 761 <tree>::
 762         Indicates a tree object name.
 763
 764 <commit>::
 765         Indicates a commit object name.
 766
 767 <tree-ish>::
 768         Indicates a tree, commit or tag object name.  A
 769         command that takes a <tree-ish> argument ultimately wants to
 770         operate on a <tree> object but automatically dereferences
 771         <commit> and <tag> objects that point at a <tree>.
 772
 773 <commit-ish>::
 774         Indicates a commit or tag object name.  A
 775         command that takes a <commit-ish> argument ultimately wants to
 776         operate on a <commit> object but automatically dereferences
 777         <tag> objects that point at a <commit>.
 778
 779 <type>::
 780         Indicates that an object type is required.
 781         Currently one of: `blob`, `tree`, `commit`, or `tag`.
 782
 783 <file>::
 784         Indicates a filename - almost always relative to the
 785         root of the tree structure `GIT_INDEX_FILE` describes.
 786
 787 Symbolic Identifiers
 788 --------------------
 789 Any Git command accepting any <object> can also use the following
 790 symbolic notation:
 791
 792 HEAD::
 793         indicates the head of the current branch.
 794
 795 <tag>::
 796         a valid tag 'name'
 797         (i.e. a `refs/tags/<tag>` reference).
 798
 799 <head>::
 800         a valid head 'name'
 801         (i.e. a `refs/heads/<head>` reference).
 802
 803 For a more complete list of ways to spell object names, see
 804 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
 805
 806
 807 File/Directory Structure
 808 ------------------------
 809
 810 Please see the linkgit:gitrepository-layout[5] document.
 811
 812 Read linkgit:githooks[5] for more details about each hook.
 813
 814 Higher level SCMs may provide and manage additional information in the
 815 `$GIT_DIR`.
 816
 817
 818 Terminology
 819 -----------
 820 Please see linkgit:gitglossary[7].
 821
 822
 823 Environment Variables
 824 ---------------------
 825 Various Git commands use the following environment variables:
 826
 827 The Git Repository
 828 ~~~~~~~~~~~~~~~~~~
 829 These environment variables apply to 'all' core Git commands. Nb: it
 830 is worth noting that they may be used/overridden by SCMS sitting above
 831 Git so take care if using a foreign front-end.
 832
 833 `GIT_INDEX_FILE`::
 834         This environment allows the specification of an alternate
 835         index file. If not specified, the default of `$GIT_DIR/index`
 836         is used.
 837
 838 `GIT_INDEX_VERSION`::
 839         This environment variable allows the specification of an index
 840         version for new repositories.  It won't affect existing index
 841         files.  By default index file version 2 or 3 is used. See
 842         linkgit:git-update-index[1] for more information.
 843
 844 `GIT_OBJECT_DIRECTORY`::
 845         If the object storage directory is specified via this
 846         environment variable then the sha1 directories are created
 847         underneath - otherwise the default `$GIT_DIR/objects`
 848         directory is used.
 849
 850 `GIT_ALTERNATE_OBJECT_DIRECTORIES`::
 851         Due to the immutable nature of Git objects, old objects can be
 852         archived into shared, read-only directories. This variable
 853         specifies a ":" separated (on Windows ";" separated) list
 854         of Git object directories which can be used to search for Git
 855         objects. New objects will not be written to these directories.
 856
 857 `GIT_DIR`::
 858         If the `GIT_DIR` environment variable is set then it
 859         specifies a path to use instead of the default `.git`
 860         for the base of the repository.
 861         The `--git-dir` command-line option also sets this value.
 862
 863 `GIT_WORK_TREE`::
 864         Set the path to the root of the working tree.
 865         This can also be controlled by the `--work-tree` command-line
 866         option and the core.worktree configuration variable.
 867
 868 `GIT_NAMESPACE`::
 869         Set the Git namespace; see linkgit:gitnamespaces[7] for details.
 870         The `--namespace` command-line option also sets this value.
 871
 872 `GIT_CEILING_DIRECTORIES`::
 873         This should be a colon-separated list of absolute paths.  If
 874         set, it is a list of directories that Git should not chdir up
 875         into while looking for a repository directory (useful for
 876         excluding slow-loading network directories).  It will not
 877         exclude the current working directory or a GIT_DIR set on the
 878         command line or in the environment.  Normally, Git has to read
 879         the entries in this list and resolve any symlink that
 880         might be present in order to compare them with the current
 881         directory.  However, if even this access is slow, you
 882         can add an empty entry to the list to tell Git that the
 883         subsequent entries are not symlinks and needn't be resolved;
 884         e.g.,
 885         `GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink`.
 886
 887 `GIT_DISCOVERY_ACROSS_FILESYSTEM`::
 888         When run in a directory that does not have ".git" repository
 889         directory, Git tries to find such a directory in the parent
 890         directories to find the top of the working tree, but by default it
 891         does not cross filesystem boundaries.  This environment variable
 892         can be set to true to tell Git not to stop at filesystem
 893         boundaries.  Like `GIT_CEILING_DIRECTORIES`, this will not affect
 894         an explicit repository directory set via `GIT_DIR` or on the
 895         command line.
 896
 897 `GIT_COMMON_DIR`::
 898         If this variable is set to a path, non-worktree files that are
 899         normally in $GIT_DIR will be taken from this path
 900         instead. Worktree-specific files such as HEAD or index are
 901         taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
 902         linkgit:git-worktree[1] for
 903         details. This variable has lower precedence than other path
 904         variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
 905
 906 Git Commits
 907 ~~~~~~~~~~~
 908 `GIT_AUTHOR_NAME`::
 909 `GIT_AUTHOR_EMAIL`::
 910 `GIT_AUTHOR_DATE`::
 911 `GIT_COMMITTER_NAME`::
 912 `GIT_COMMITTER_EMAIL`::
 913 `GIT_COMMITTER_DATE`::
 914 'EMAIL'::
 915         see linkgit:git-commit-tree[1]
 916
 917 Git Diffs
 918 ~~~~~~~~~
 919 `GIT_DIFF_OPTS`::
 920         Only valid setting is "--unified=??" or "-u??" to set the
 921         number of context lines shown when a unified diff is created.
 922         This takes precedence over any "-U" or "--unified" option
 923         value passed on the Git diff command line.
 924
 925 `GIT_EXTERNAL_DIFF`::
 926         When the environment variable `GIT_EXTERNAL_DIFF` is set, the
 927         program named by it is called, instead of the diff invocation
 928         described above.  For a path that is added, removed, or modified,
 929         `GIT_EXTERNAL_DIFF` is called with 7 parameters:
 930
 931         path old-file old-hex old-mode new-file new-hex new-mode
 932 +
 933 where:
 934
 935         <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
 936                          contents of <old|new>,
 937         <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
 938         <old|new>-mode:: are the octal representation of the file modes.
 939 +
 940 The file parameters can point at the user's working file
 941 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
 942 when a new file is added), or a temporary file (e.g. `old-file` in the
 943 index).  `GIT_EXTERNAL_DIFF` should not worry about unlinking the
 944 temporary file --- it is removed when `GIT_EXTERNAL_DIFF` exits.
 945 +
 946 For a path that is unmerged, `GIT_EXTERNAL_DIFF` is called with 1
 947 parameter, <path>.
 948 +
 949 For each path `GIT_EXTERNAL_DIFF` is called, two environment variables,
 950 `GIT_DIFF_PATH_COUNTER` and `GIT_DIFF_PATH_TOTAL` are set.
 951
 952 `GIT_DIFF_PATH_COUNTER`::
 953         A 1-based counter incremented by one for every path.
 954
 955 `GIT_DIFF_PATH_TOTAL`::
 956         The total number of paths.
 957
 958 other
 959 ~~~~~
 960 `GIT_MERGE_VERBOSITY`::
 961         A number controlling the amount of output shown by
 962         the recursive merge strategy.  Overrides merge.verbosity.
 963         See linkgit:git-merge[1]
 964
 965 `GIT_PAGER`::
 966         This environment variable overrides `$PAGER`. If it is set
 967         to an empty string or to the value "cat", Git will not launch
 968         a pager.  See also the `core.pager` option in
 969         linkgit:git-config[1].
 970
 971 `GIT_EDITOR`::
 972         This environment variable overrides `$EDITOR` and `$VISUAL`.
 973         It is used by several Git commands when, on interactive mode,
 974         an editor is to be launched. See also linkgit:git-var[1]
 975         and the `core.editor` option in linkgit:git-config[1].
 976
 977 `GIT_SSH`::
 978 `GIT_SSH_COMMAND`::
 979         If either of these environment variables is set then 'git fetch'
 980         and 'git push' will use the specified command instead of 'ssh'
 981         when they need to connect to a remote system.
 982         The command will be given exactly two or four arguments: the
 983         'username@host' (or just 'host') from the URL and the shell
 984         command to execute on that remote system, optionally preceded by
 985         `-p` (literally) and the 'port' from the URL when it specifies
 986         something other than the default SSH port.
 987 +
 988 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
 989 by the shell, which allows additional arguments to be included.
 990 `$GIT_SSH` on the other hand must be just the path to a program
 991 (which can be a wrapper shell script, if additional arguments are
 992 needed).
 993 +
 994 Usually it is easier to configure any desired options through your
 995 personal `.ssh/config` file.  Please consult your ssh documentation
 996 for further details.
 997
 998 `GIT_ASKPASS`::
 999         If this environment variable is set, then Git commands which need to
1000         acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
1001         will call this program with a suitable prompt as command-line argument
1002         and read the password from its STDOUT. See also the `core.askPass`
1003         option in linkgit:git-config[1].
1004
1005 `GIT_TERMINAL_PROMPT`::
1006         If this environment variable is set to `0`, git will not prompt
1007         on the terminal (e.g., when asking for HTTP authentication).
1008
1009 `GIT_CONFIG_NOSYSTEM`::
1010         Whether to skip reading settings from the system-wide
1011         `$(prefix)/etc/gitconfig` file.  This environment variable can
1012         be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
1013         predictable environment for a picky script, or you can set it
1014         temporarily to avoid using a buggy `/etc/gitconfig` file while
1015         waiting for someone with sufficient permissions to fix it.
1016
1017 `GIT_FLUSH`::
1018         If this environment variable is set to "1", then commands such
1019         as 'git blame' (in incremental mode), 'git rev-list', 'git log',
1020         'git check-attr' and 'git check-ignore' will
1021         force a flush of the output stream after each record have been
1022         flushed. If this
1023         variable is set to "0", the output of these commands will be done
1024         using completely buffered I/O.   If this environment variable is
1025         not set, Git will choose buffered or record-oriented flushing
1026         based on whether stdout appears to be redirected to a file or not.
1027
1028 `GIT_TRACE`::
1029         Enables general trace messages, e.g. alias expansion, built-in
1030         command execution and external command execution.
1031 +
1032 If this variable is set to "1", "2" or "true" (comparison
1033 is case insensitive), trace messages will be printed to
1034 stderr.
1035 +
1036 If the variable is set to an integer value greater than 2
1037 and lower than 10 (strictly) then Git will interpret this
1038 value as an open file descriptor and will try to write the
1039 trace messages into this file descriptor.
1040 +
1041 Alternatively, if the variable is set to an absolute path
1042 (starting with a '/' character), Git will interpret this
1043 as a file path and will try to write the trace messages
1044 into it.
1045 +
1046 Unsetting the variable, or setting it to empty, "0" or
1047 "false" (case insensitive) disables trace messages.
1048
1049 `GIT_TRACE_PACK_ACCESS`::
1050         Enables trace messages for all accesses to any packs. For each
1051         access, the pack file name and an offset in the pack is
1052         recorded. This may be helpful for troubleshooting some
1053         pack-related performance problems.
1054         See `GIT_TRACE` for available trace output options.
1055
1056 `GIT_TRACE_PACKET`::
1057         Enables trace messages for all packets coming in or out of a
1058         given program. This can help with debugging object negotiation
1059         or other protocol issues. Tracing is turned off at a packet
1060         starting with "PACK" (but see `GIT_TRACE_PACKFILE` below).
1061         See `GIT_TRACE` for available trace output options.
1062
1063 `GIT_TRACE_PACKFILE`::
1064         Enables tracing of packfiles sent or received by a
1065         given program. Unlike other trace output, this trace is
1066         verbatim: no headers, and no quoting of binary data. You almost
1067         certainly want to direct into a file (e.g.,
1068         `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1069         the terminal or mixing it with other trace output.
1070 +
1071 Note that this is currently only implemented for the client side
1072 of clones and fetches.
1073
1074 `GIT_TRACE_PERFORMANCE`::
1075         Enables performance related trace messages, e.g. total execution
1076         time of each Git command.
1077         See `GIT_TRACE` for available trace output options.
1078
1079 `GIT_TRACE_SETUP`::
1080         Enables trace messages printing the .git, working tree and current
1081         working directory after Git has completed its setup phase.
1082         See `GIT_TRACE` for available trace output options.
1083
1084 `GIT_TRACE_SHALLOW`::
1085         Enables trace messages that can help debugging fetching /
1086         cloning of shallow repositories.
1087         See `GIT_TRACE` for available trace output options.
1088
1089 `GIT_TRACE_CURL`::
1090         Enables a curl full trace dump of all incoming and outgoing data,
1091         including descriptive information, of the git transport protocol.
1092         This is similar to doing curl `--trace-ascii` on the command line.
1093         This option overrides setting the `GIT_CURL_VERBOSE` environment
1094         variable.
1095         See `GIT_TRACE` for available trace output options.
1096
1097 `GIT_LITERAL_PATHSPECS`::
1098         Setting this variable to `1` will cause Git to treat all
1099         pathspecs literally, rather than as glob patterns. For example,
1100         running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1101         for commits that touch the path `*.c`, not any paths that the
1102         glob `*.c` matches. You might want this if you are feeding
1103         literal paths to Git (e.g., paths previously given to you by
1104         `git ls-tree`, `--raw` diff output, etc).
1105
1106 `GIT_GLOB_PATHSPECS`::
1107         Setting this variable to `1` will cause Git to treat all
1108         pathspecs as glob patterns (aka "glob" magic).
1109
1110 `GIT_NOGLOB_PATHSPECS`::
1111         Setting this variable to `1` will cause Git to treat all
1112         pathspecs as literal (aka "literal" magic).
1113
1114 `GIT_ICASE_PATHSPECS`::
1115         Setting this variable to `1` will cause Git to treat all
1116         pathspecs as case-insensitive.
1117
1118 `GIT_REFLOG_ACTION`::
1119         When a ref is updated, reflog entries are created to keep
1120         track of the reason why the ref was updated (which is
1121         typically the name of the high-level command that updated
1122         the ref), in addition to the old and new values of the ref.
1123         A scripted Porcelain command can use set_reflog_action
1124         helper function in `git-sh-setup` to set its name to this
1125         variable when it is invoked as the top level command by the
1126         end user, to be recorded in the body of the reflog.
1127
1128 `GIT_REF_PARANOIA`::
1129         If set to `1`, include broken or badly named refs when iterating
1130         over lists of refs. In a normal, non-corrupted repository, this
1131         does nothing. However, enabling it may help git to detect and
1132         abort some operations in the presence of broken refs. Git sets
1133         this variable automatically when performing destructive
1134         operations like linkgit:git-prune[1]. You should not need to set
1135         it yourself unless you want to be paranoid about making sure
1136         an operation has touched every ref (e.g., because you are
1137         cloning a repository to make a backup).
1138
1139 `GIT_ALLOW_PROTOCOL`::
1140         If set, provide a colon-separated list of protocols which are
1141         allowed to be used with fetch/push/clone. This is useful to
1142         restrict recursive submodule initialization from an untrusted
1143         repository. Any protocol not mentioned will be disallowed (i.e.,
1144         this is a whitelist, not a blacklist). If the variable is not
1145         set at all, all protocols are enabled.  The protocol names
1146         currently used by git are:
1147
1148           - `file`: any local file-based path (including `file://` URLs,
1149             or local paths)
1150
1151           - `git`: the anonymous git protocol over a direct TCP
1152             connection (or proxy, if configured)
1153
1154           - `ssh`: git over ssh (including `host:path` syntax,
1155             `ssh://`, etc).
1156
1157           - `http`: git over http, both "smart http" and "dumb http".
1158             Note that this does _not_ include `https`; if you want both,
1159             you should specify both as `http:https`.
1160
1161           - any external helpers are named by their protocol (e.g., use
1162             `hg` to allow the `git-remote-hg` helper)
1163
1164
1165 Discussion[[Discussion]]
1166 ------------------------
1167
1168 More detail on the following is available from the
1169 link:user-manual.html#git-concepts[Git concepts chapter of the
1170 user-manual] and linkgit:gitcore-tutorial[7].
1171
1172 A Git project normally consists of a working directory with a ".git"
1173 subdirectory at the top level.  The .git directory contains, among other
1174 things, a compressed object database representing the complete history
1175 of the project, an "index" file which links that history to the current
1176 contents of the working tree, and named pointers into that history such
1177 as tags and branch heads.
1178
1179 The object database contains objects of three main types: blobs, which
1180 hold file data; trees, which point to blobs and other trees to build up
1181 directory hierarchies; and commits, which each reference a single tree
1182 and some number of parent commits.
1183
1184 The commit, equivalent to what other systems call a "changeset" or
1185 "version", represents a step in the project's history, and each parent
1186 represents an immediately preceding step.  Commits with more than one
1187 parent represent merges of independent lines of development.
1188
1189 All objects are named by the SHA-1 hash of their contents, normally
1190 written as a string of 40 hex digits.  Such names are globally unique.
1191 The entire history leading up to a commit can be vouched for by signing
1192 just that commit.  A fourth object type, the tag, is provided for this
1193 purpose.
1194
1195 When first created, objects are stored in individual files, but for
1196 efficiency may later be compressed together into "pack files".
1197
1198 Named pointers called refs mark interesting points in history.  A ref
1199 may contain the SHA-1 name of an object or the name of another ref.  Refs
1200 with names beginning `ref/head/` contain the SHA-1 name of the most
1201 recent commit (or "head") of a branch under development.  SHA-1 names of
1202 tags of interest are stored under `ref/tags/`.  A special ref named
1203 `HEAD` contains the name of the currently checked-out branch.
1204
1205 The index file is initialized with a list of all paths and, for each
1206 path, a blob object and a set of attributes.  The blob object represents
1207 the contents of the file as of the head of the current branch.  The
1208 attributes (last modified time, size, etc.) are taken from the
1209 corresponding file in the working tree.  Subsequent changes to the
1210 working tree can be found by comparing these attributes.  The index may
1211 be updated with new content, and new commits may be created from the
1212 content stored in the index.
1213
1214 The index is also capable of storing multiple entries (called "stages")
1215 for a given pathname.  These stages are used to hold the various
1216 unmerged version of a file when a merge is in progress.
1217
1218 FURTHER DOCUMENTATION
1219 ---------------------
1220
1221 See the references in the "description" section to get started
1222 using Git.  The following is probably more detail than necessary
1223 for a first-time user.
1224
1225 The link:user-manual.html#git-concepts[Git concepts chapter of the
1226 user-manual] and linkgit:gitcore-tutorial[7] both provide
1227 introductions to the underlying Git architecture.
1228
1229 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1230
1231 See also the link:howto-index.html[howto] documents for some useful
1232 examples.
1233
1234 The internals are documented in the
1235 link:technical/api-index.html[Git API documentation].
1236
1237 Users migrating from CVS may also want to
1238 read linkgit:gitcvs-migration[7].
1239
1240
1241 Authors
1242 -------
1243 Git was started by Linus Torvalds, and is currently maintained by Junio
1244 C Hamano. Numerous contributions have come from the Git mailing list
1245 <git@vger.kernel.org>.  http://www.openhub.net/p/git/contributors/summary
1246 gives you a more complete list of contributors.
1247
1248 If you have a clone of git.git itself, the
1249 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1250 the authors for specific parts of the project.
1251
1252 Reporting Bugs
1253 --------------
1254
1255 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1256 development and maintenance is primarily done.  You do not have to be
1257 subscribed to the list to send a message there.
1258
1259 SEE ALSO
1260 --------
1261 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1262 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1263 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1264 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1265 linkgit:gitworkflows[7]
1266
1267 GIT
1268 ---
1269 Part of the linkgit:git[1] suite