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