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