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