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