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