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