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