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