6 git - the stupid content tracker
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>]
20 Git is a fast, scalable, distributed revision control system with an
21 unusually rich command set that provides both high-level operations
22 and full access to internals.
24 See linkgit:gittutorial[7] to get started, then see
25 linkgit:giteveryday[7] for a useful minimum set of
26 commands. The link:user-manual.html[Git User's Manual] has a more
27 in-depth introduction.
29 After you mastered the basic concepts, you can come back to this
30 page to learn what commands Git offers. You can learn more about
31 individual Git commands with "git help command". linkgit:gitcli[7]
32 manual page gives you an overview of the command-line command syntax.
34 Formatted and hyperlinked version of the latest Git documentation
35 can be viewed at `http://git-htmldocs.googlecode.com/git/git.html`.
41 You are reading the documentation for the latest (possibly
42 unreleased) version of Git, that is available from the 'master'
43 branch of the `git.git` repository.
44 Documentation for older releases are available here:
46 * link:v2.7.0/git.html[documentation for release 2.7]
49 link:RelNotes/2.7.0.txt[2.7].
51 * link:v2.6.5/git.html[documentation for release 2.6.5]
54 link:RelNotes/2.6.5.txt[2.6.5],
55 link:RelNotes/2.6.4.txt[2.6.4],
56 link:RelNotes/2.6.3.txt[2.6.3],
57 link:RelNotes/2.6.2.txt[2.6.2],
58 link:RelNotes/2.6.1.txt[2.6.1],
59 link:RelNotes/2.6.0.txt[2.6].
61 * link:v2.5.4/git.html[documentation for release 2.5.4]
64 link:RelNotes/2.5.4.txt[2.5.4],
65 link:RelNotes/2.5.3.txt[2.5.3],
66 link:RelNotes/2.5.2.txt[2.5.2],
67 link:RelNotes/2.5.1.txt[2.5.1],
68 link:RelNotes/2.5.0.txt[2.5].
70 * link:v2.4.10/git.html[documentation for release 2.4.10]
73 link:RelNotes/2.4.10.txt[2.4.10],
74 link:RelNotes/2.4.9.txt[2.4.9],
75 link:RelNotes/2.4.8.txt[2.4.8],
76 link:RelNotes/2.4.7.txt[2.4.7],
77 link:RelNotes/2.4.6.txt[2.4.6],
78 link:RelNotes/2.4.5.txt[2.4.5],
79 link:RelNotes/2.4.4.txt[2.4.4],
80 link:RelNotes/2.4.3.txt[2.4.3],
81 link:RelNotes/2.4.2.txt[2.4.2],
82 link:RelNotes/2.4.1.txt[2.4.1],
83 link:RelNotes/2.4.0.txt[2.4].
85 * link:v2.3.10/git.html[documentation for release 2.3.10]
88 link:RelNotes/2.3.10.txt[2.3.10],
89 link:RelNotes/2.3.9.txt[2.3.9],
90 link:RelNotes/2.3.8.txt[2.3.8],
91 link:RelNotes/2.3.7.txt[2.3.7],
92 link:RelNotes/2.3.6.txt[2.3.6],
93 link:RelNotes/2.3.5.txt[2.3.5],
94 link:RelNotes/2.3.4.txt[2.3.4],
95 link:RelNotes/2.3.3.txt[2.3.3],
96 link:RelNotes/2.3.2.txt[2.3.2],
97 link:RelNotes/2.3.1.txt[2.3.1],
98 link:RelNotes/2.3.0.txt[2.3].
100 * link:v2.2.3/git.html[documentation for release 2.2.3]
103 link:RelNotes/2.2.3.txt[2.2.3],
104 link:RelNotes/2.2.2.txt[2.2.2],
105 link:RelNotes/2.2.1.txt[2.2.1],
106 link:RelNotes/2.2.0.txt[2.2].
108 * link:v2.1.4/git.html[documentation for release 2.1.4]
111 link:RelNotes/2.1.4.txt[2.1.4],
112 link:RelNotes/2.1.3.txt[2.1.3],
113 link:RelNotes/2.1.2.txt[2.1.2],
114 link:RelNotes/2.1.1.txt[2.1.1],
115 link:RelNotes/2.1.0.txt[2.1].
117 * link:v2.0.5/git.html[documentation for release 2.0.5]
120 link:RelNotes/2.0.5.txt[2.0.5],
121 link:RelNotes/2.0.4.txt[2.0.4],
122 link:RelNotes/2.0.3.txt[2.0.3],
123 link:RelNotes/2.0.2.txt[2.0.2],
124 link:RelNotes/2.0.1.txt[2.0.1],
125 link:RelNotes/2.0.0.txt[2.0.0].
127 * link:v1.9.5/git.html[documentation for release 1.9.5]
130 link:RelNotes/1.9.5.txt[1.9.5],
131 link:RelNotes/1.9.4.txt[1.9.4],
132 link:RelNotes/1.9.3.txt[1.9.3],
133 link:RelNotes/1.9.2.txt[1.9.2],
134 link:RelNotes/1.9.1.txt[1.9.1],
135 link:RelNotes/1.9.0.txt[1.9.0].
137 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
140 link:RelNotes/1.8.5.6.txt[1.8.5.6],
141 link:RelNotes/1.8.5.5.txt[1.8.5.5],
142 link:RelNotes/1.8.5.4.txt[1.8.5.4],
143 link:RelNotes/1.8.5.3.txt[1.8.5.3],
144 link:RelNotes/1.8.5.2.txt[1.8.5.2],
145 link:RelNotes/1.8.5.1.txt[1.8.5.1],
146 link:RelNotes/1.8.5.txt[1.8.5].
148 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
151 link:RelNotes/1.8.4.5.txt[1.8.4.5],
152 link:RelNotes/1.8.4.4.txt[1.8.4.4],
153 link:RelNotes/1.8.4.3.txt[1.8.4.3],
154 link:RelNotes/1.8.4.2.txt[1.8.4.2],
155 link:RelNotes/1.8.4.1.txt[1.8.4.1],
156 link:RelNotes/1.8.4.txt[1.8.4].
158 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
161 link:RelNotes/1.8.3.4.txt[1.8.3.4],
162 link:RelNotes/1.8.3.3.txt[1.8.3.3],
163 link:RelNotes/1.8.3.2.txt[1.8.3.2],
164 link:RelNotes/1.8.3.1.txt[1.8.3.1],
165 link:RelNotes/1.8.3.txt[1.8.3].
167 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
170 link:RelNotes/1.8.2.3.txt[1.8.2.3],
171 link:RelNotes/1.8.2.2.txt[1.8.2.2],
172 link:RelNotes/1.8.2.1.txt[1.8.2.1],
173 link:RelNotes/1.8.2.txt[1.8.2].
175 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
178 link:RelNotes/1.8.1.6.txt[1.8.1.6],
179 link:RelNotes/1.8.1.5.txt[1.8.1.5],
180 link:RelNotes/1.8.1.4.txt[1.8.1.4],
181 link:RelNotes/1.8.1.3.txt[1.8.1.3],
182 link:RelNotes/1.8.1.2.txt[1.8.1.2],
183 link:RelNotes/1.8.1.1.txt[1.8.1.1],
184 link:RelNotes/1.8.1.txt[1.8.1].
186 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
189 link:RelNotes/1.8.0.3.txt[1.8.0.3],
190 link:RelNotes/1.8.0.2.txt[1.8.0.2],
191 link:RelNotes/1.8.0.1.txt[1.8.0.1],
192 link:RelNotes/1.8.0.txt[1.8.0].
194 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
197 link:RelNotes/1.7.12.4.txt[1.7.12.4],
198 link:RelNotes/1.7.12.3.txt[1.7.12.3],
199 link:RelNotes/1.7.12.2.txt[1.7.12.2],
200 link:RelNotes/1.7.12.1.txt[1.7.12.1],
201 link:RelNotes/1.7.12.txt[1.7.12].
203 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
206 link:RelNotes/1.7.11.7.txt[1.7.11.7],
207 link:RelNotes/1.7.11.6.txt[1.7.11.6],
208 link:RelNotes/1.7.11.5.txt[1.7.11.5],
209 link:RelNotes/1.7.11.4.txt[1.7.11.4],
210 link:RelNotes/1.7.11.3.txt[1.7.11.3],
211 link:RelNotes/1.7.11.2.txt[1.7.11.2],
212 link:RelNotes/1.7.11.1.txt[1.7.11.1],
213 link:RelNotes/1.7.11.txt[1.7.11].
215 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
218 link:RelNotes/1.7.10.5.txt[1.7.10.5],
219 link:RelNotes/1.7.10.4.txt[1.7.10.4],
220 link:RelNotes/1.7.10.3.txt[1.7.10.3],
221 link:RelNotes/1.7.10.2.txt[1.7.10.2],
222 link:RelNotes/1.7.10.1.txt[1.7.10.1],
223 link:RelNotes/1.7.10.txt[1.7.10].
225 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
228 link:RelNotes/1.7.9.7.txt[1.7.9.7],
229 link:RelNotes/1.7.9.6.txt[1.7.9.6],
230 link:RelNotes/1.7.9.5.txt[1.7.9.5],
231 link:RelNotes/1.7.9.4.txt[1.7.9.4],
232 link:RelNotes/1.7.9.3.txt[1.7.9.3],
233 link:RelNotes/1.7.9.2.txt[1.7.9.2],
234 link:RelNotes/1.7.9.1.txt[1.7.9.1],
235 link:RelNotes/1.7.9.txt[1.7.9].
237 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
240 link:RelNotes/1.7.8.6.txt[1.7.8.6],
241 link:RelNotes/1.7.8.5.txt[1.7.8.5],
242 link:RelNotes/1.7.8.4.txt[1.7.8.4],
243 link:RelNotes/1.7.8.3.txt[1.7.8.3],
244 link:RelNotes/1.7.8.2.txt[1.7.8.2],
245 link:RelNotes/1.7.8.1.txt[1.7.8.1],
246 link:RelNotes/1.7.8.txt[1.7.8].
248 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
251 link:RelNotes/1.7.7.7.txt[1.7.7.7],
252 link:RelNotes/1.7.7.6.txt[1.7.7.6],
253 link:RelNotes/1.7.7.5.txt[1.7.7.5],
254 link:RelNotes/1.7.7.4.txt[1.7.7.4],
255 link:RelNotes/1.7.7.3.txt[1.7.7.3],
256 link:RelNotes/1.7.7.2.txt[1.7.7.2],
257 link:RelNotes/1.7.7.1.txt[1.7.7.1],
258 link:RelNotes/1.7.7.txt[1.7.7].
260 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
263 link:RelNotes/1.7.6.6.txt[1.7.6.6],
264 link:RelNotes/1.7.6.5.txt[1.7.6.5],
265 link:RelNotes/1.7.6.4.txt[1.7.6.4],
266 link:RelNotes/1.7.6.3.txt[1.7.6.3],
267 link:RelNotes/1.7.6.2.txt[1.7.6.2],
268 link:RelNotes/1.7.6.1.txt[1.7.6.1],
269 link:RelNotes/1.7.6.txt[1.7.6].
271 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
274 link:RelNotes/1.7.5.4.txt[1.7.5.4],
275 link:RelNotes/1.7.5.3.txt[1.7.5.3],
276 link:RelNotes/1.7.5.2.txt[1.7.5.2],
277 link:RelNotes/1.7.5.1.txt[1.7.5.1],
278 link:RelNotes/1.7.5.txt[1.7.5].
280 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
283 link:RelNotes/1.7.4.5.txt[1.7.4.5],
284 link:RelNotes/1.7.4.4.txt[1.7.4.4],
285 link:RelNotes/1.7.4.3.txt[1.7.4.3],
286 link:RelNotes/1.7.4.2.txt[1.7.4.2],
287 link:RelNotes/1.7.4.1.txt[1.7.4.1],
288 link:RelNotes/1.7.4.txt[1.7.4].
290 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
293 link:RelNotes/1.7.3.5.txt[1.7.3.5],
294 link:RelNotes/1.7.3.4.txt[1.7.3.4],
295 link:RelNotes/1.7.3.3.txt[1.7.3.3],
296 link:RelNotes/1.7.3.2.txt[1.7.3.2],
297 link:RelNotes/1.7.3.1.txt[1.7.3.1],
298 link:RelNotes/1.7.3.txt[1.7.3].
300 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
303 link:RelNotes/1.7.2.5.txt[1.7.2.5],
304 link:RelNotes/1.7.2.4.txt[1.7.2.4],
305 link:RelNotes/1.7.2.3.txt[1.7.2.3],
306 link:RelNotes/1.7.2.2.txt[1.7.2.2],
307 link:RelNotes/1.7.2.1.txt[1.7.2.1],
308 link:RelNotes/1.7.2.txt[1.7.2].
310 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
313 link:RelNotes/1.7.1.4.txt[1.7.1.4],
314 link:RelNotes/1.7.1.3.txt[1.7.1.3],
315 link:RelNotes/1.7.1.2.txt[1.7.1.2],
316 link:RelNotes/1.7.1.1.txt[1.7.1.1],
317 link:RelNotes/1.7.1.txt[1.7.1].
319 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
322 link:RelNotes/1.7.0.9.txt[1.7.0.9],
323 link:RelNotes/1.7.0.8.txt[1.7.0.8],
324 link:RelNotes/1.7.0.7.txt[1.7.0.7],
325 link:RelNotes/1.7.0.6.txt[1.7.0.6],
326 link:RelNotes/1.7.0.5.txt[1.7.0.5],
327 link:RelNotes/1.7.0.4.txt[1.7.0.4],
328 link:RelNotes/1.7.0.3.txt[1.7.0.3],
329 link:RelNotes/1.7.0.2.txt[1.7.0.2],
330 link:RelNotes/1.7.0.1.txt[1.7.0.1],
331 link:RelNotes/1.7.0.txt[1.7.0].
333 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
336 link:RelNotes/1.6.6.3.txt[1.6.6.3],
337 link:RelNotes/1.6.6.2.txt[1.6.6.2],
338 link:RelNotes/1.6.6.1.txt[1.6.6.1],
339 link:RelNotes/1.6.6.txt[1.6.6].
341 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
344 link:RelNotes/1.6.5.9.txt[1.6.5.9],
345 link:RelNotes/1.6.5.8.txt[1.6.5.8],
346 link:RelNotes/1.6.5.7.txt[1.6.5.7],
347 link:RelNotes/1.6.5.6.txt[1.6.5.6],
348 link:RelNotes/1.6.5.5.txt[1.6.5.5],
349 link:RelNotes/1.6.5.4.txt[1.6.5.4],
350 link:RelNotes/1.6.5.3.txt[1.6.5.3],
351 link:RelNotes/1.6.5.2.txt[1.6.5.2],
352 link:RelNotes/1.6.5.1.txt[1.6.5.1],
353 link:RelNotes/1.6.5.txt[1.6.5].
355 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
358 link:RelNotes/1.6.4.5.txt[1.6.4.5],
359 link:RelNotes/1.6.4.4.txt[1.6.4.4],
360 link:RelNotes/1.6.4.3.txt[1.6.4.3],
361 link:RelNotes/1.6.4.2.txt[1.6.4.2],
362 link:RelNotes/1.6.4.1.txt[1.6.4.1],
363 link:RelNotes/1.6.4.txt[1.6.4].
365 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
368 link:RelNotes/1.6.3.4.txt[1.6.3.4],
369 link:RelNotes/1.6.3.3.txt[1.6.3.3],
370 link:RelNotes/1.6.3.2.txt[1.6.3.2],
371 link:RelNotes/1.6.3.1.txt[1.6.3.1],
372 link:RelNotes/1.6.3.txt[1.6.3].
375 link:RelNotes/1.6.2.5.txt[1.6.2.5],
376 link:RelNotes/1.6.2.4.txt[1.6.2.4],
377 link:RelNotes/1.6.2.3.txt[1.6.2.3],
378 link:RelNotes/1.6.2.2.txt[1.6.2.2],
379 link:RelNotes/1.6.2.1.txt[1.6.2.1],
380 link:RelNotes/1.6.2.txt[1.6.2].
382 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
385 link:RelNotes/1.6.1.3.txt[1.6.1.3],
386 link:RelNotes/1.6.1.2.txt[1.6.1.2],
387 link:RelNotes/1.6.1.1.txt[1.6.1.1],
388 link:RelNotes/1.6.1.txt[1.6.1].
390 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
393 link:RelNotes/1.6.0.6.txt[1.6.0.6],
394 link:RelNotes/1.6.0.5.txt[1.6.0.5],
395 link:RelNotes/1.6.0.4.txt[1.6.0.4],
396 link:RelNotes/1.6.0.3.txt[1.6.0.3],
397 link:RelNotes/1.6.0.2.txt[1.6.0.2],
398 link:RelNotes/1.6.0.1.txt[1.6.0.1],
399 link:RelNotes/1.6.0.txt[1.6.0].
401 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
404 link:RelNotes/1.5.6.6.txt[1.5.6.6],
405 link:RelNotes/1.5.6.5.txt[1.5.6.5],
406 link:RelNotes/1.5.6.4.txt[1.5.6.4],
407 link:RelNotes/1.5.6.3.txt[1.5.6.3],
408 link:RelNotes/1.5.6.2.txt[1.5.6.2],
409 link:RelNotes/1.5.6.1.txt[1.5.6.1],
410 link:RelNotes/1.5.6.txt[1.5.6].
412 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
415 link:RelNotes/1.5.5.6.txt[1.5.5.6],
416 link:RelNotes/1.5.5.5.txt[1.5.5.5],
417 link:RelNotes/1.5.5.4.txt[1.5.5.4],
418 link:RelNotes/1.5.5.3.txt[1.5.5.3],
419 link:RelNotes/1.5.5.2.txt[1.5.5.2],
420 link:RelNotes/1.5.5.1.txt[1.5.5.1],
421 link:RelNotes/1.5.5.txt[1.5.5].
423 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
426 link:RelNotes/1.5.4.7.txt[1.5.4.7],
427 link:RelNotes/1.5.4.6.txt[1.5.4.6],
428 link:RelNotes/1.5.4.5.txt[1.5.4.5],
429 link:RelNotes/1.5.4.4.txt[1.5.4.4],
430 link:RelNotes/1.5.4.3.txt[1.5.4.3],
431 link:RelNotes/1.5.4.2.txt[1.5.4.2],
432 link:RelNotes/1.5.4.1.txt[1.5.4.1],
433 link:RelNotes/1.5.4.txt[1.5.4].
435 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
438 link:RelNotes/1.5.3.8.txt[1.5.3.8],
439 link:RelNotes/1.5.3.7.txt[1.5.3.7],
440 link:RelNotes/1.5.3.6.txt[1.5.3.6],
441 link:RelNotes/1.5.3.5.txt[1.5.3.5],
442 link:RelNotes/1.5.3.4.txt[1.5.3.4],
443 link:RelNotes/1.5.3.3.txt[1.5.3.3],
444 link:RelNotes/1.5.3.2.txt[1.5.3.2],
445 link:RelNotes/1.5.3.1.txt[1.5.3.1],
446 link:RelNotes/1.5.3.txt[1.5.3].
448 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
451 link:RelNotes/1.5.2.5.txt[1.5.2.5],
452 link:RelNotes/1.5.2.4.txt[1.5.2.4],
453 link:RelNotes/1.5.2.3.txt[1.5.2.3],
454 link:RelNotes/1.5.2.2.txt[1.5.2.2],
455 link:RelNotes/1.5.2.1.txt[1.5.2.1],
456 link:RelNotes/1.5.2.txt[1.5.2].
458 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
461 link:RelNotes/1.5.1.6.txt[1.5.1.6],
462 link:RelNotes/1.5.1.5.txt[1.5.1.5],
463 link:RelNotes/1.5.1.4.txt[1.5.1.4],
464 link:RelNotes/1.5.1.3.txt[1.5.1.3],
465 link:RelNotes/1.5.1.2.txt[1.5.1.2],
466 link:RelNotes/1.5.1.1.txt[1.5.1.1],
467 link:RelNotes/1.5.1.txt[1.5.1].
469 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
472 link:RelNotes/1.5.0.7.txt[1.5.0.7],
473 link:RelNotes/1.5.0.6.txt[1.5.0.6],
474 link:RelNotes/1.5.0.5.txt[1.5.0.5],
475 link:RelNotes/1.5.0.3.txt[1.5.0.3],
476 link:RelNotes/1.5.0.2.txt[1.5.0.2],
477 link:RelNotes/1.5.0.1.txt[1.5.0.1],
478 link:RelNotes/1.5.0.txt[1.5.0].
480 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
481 link:v1.3.3/git.html[1.3.3],
482 link:v1.2.6/git.html[1.2.6],
483 link:v1.0.13/git.html[1.0.13].
492 Prints the Git suite version that the 'git' program came from.
495 Prints the synopsis and a list of the most commonly used
496 commands. If the option '--all' or '-a' is given then all
497 available commands are printed. If a Git command is named this
498 option will bring up the manual page for that command.
500 Other options are available to control how the manual page is
501 displayed. See linkgit:git-help[1] for more information,
502 because `git --help ...` is converted internally into `git
506 Run as if git was started in '<path>' instead of the current working
507 directory. When multiple `-C` options are given, each subsequent
508 non-absolute `-C <path>` is interpreted relative to the preceding `-C
511 This option affects options that expect path name like `--git-dir` and
512 `--work-tree` in that their interpretations of the path names would be
513 made relative to the working directory caused by the `-C` option. For
514 example the following invocations are equivalent:
516 git --git-dir=a.git --work-tree=b -C c status
517 git --git-dir=c/a.git --work-tree=c/b status
520 Pass a configuration parameter to the command. The value
521 given will override values from configuration files.
522 The <name> is expected in the same format as listed by
523 'git config' (subkeys separated by dots).
525 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
526 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
527 config file). Including the equals but with an empty value (like `git -c
528 foo.bar= ...`) sets `foo.bar` to the empty string.
530 --exec-path[=<path>]::
531 Path to wherever your core Git programs are installed.
532 This can also be controlled by setting the GIT_EXEC_PATH
533 environment variable. If no path is given, 'git' will print
534 the current setting and then exit.
537 Print the path, without trailing slash, where Git's HTML
538 documentation is installed and exit.
541 Print the manpath (see `man(1)`) for the man pages for
542 this version of Git and exit.
545 Print the path where the Info files documenting this
546 version of Git are installed and exit.
550 Pipe all output into 'less' (or if set, $PAGER) if standard
551 output is a terminal. This overrides the `pager.<cmd>`
552 configuration options (see the "Configuration Mechanism" section
556 Do not pipe Git output into a pager.
559 Set the path to the repository. This can also be controlled by
560 setting the GIT_DIR environment variable. It can be an absolute
561 path or relative path to current working directory.
564 Set the path to the working tree. It can be an absolute path
565 or a path relative to the current working directory.
566 This can also be controlled by setting the GIT_WORK_TREE
567 environment variable and the core.worktree configuration
568 variable (see core.worktree in linkgit:git-config[1] for a
569 more detailed discussion).
572 Set the Git namespace. See linkgit:gitnamespaces[7] for more
573 details. Equivalent to setting the `GIT_NAMESPACE` environment
577 Treat the repository as a bare repository. If GIT_DIR
578 environment is not set, it is set to the current working
581 --no-replace-objects::
582 Do not use replacement refs to replace Git objects. See
583 linkgit:git-replace[1] for more information.
585 --literal-pathspecs::
586 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
587 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
591 Add "glob" magic to all pathspec. This is equivalent to setting
592 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
593 globbing on individual pathspecs can be done using pathspec
597 Add "literal" magic to all pathspec. This is equivalent to setting
598 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
599 globbing on individual pathspecs can be done using pathspec
603 Add "icase" magic to all pathspec. This is equivalent to setting
604 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
609 We divide Git into high level ("porcelain") commands and low level
610 ("plumbing") commands.
612 High-level commands (porcelain)
613 -------------------------------
615 We separate the porcelain commands into the main commands and some
616 ancillary user utilities.
618 Main porcelain commands
619 ~~~~~~~~~~~~~~~~~~~~~~~
621 include::cmds-mainporcelain.txt[]
627 include::cmds-ancillarymanipulators.txt[]
631 include::cmds-ancillaryinterrogators.txt[]
634 Interacting with Others
635 ~~~~~~~~~~~~~~~~~~~~~~~
637 These commands are to interact with foreign SCM and with other
638 people via patch over e-mail.
640 include::cmds-foreignscminterface.txt[]
643 Low-level commands (plumbing)
644 -----------------------------
646 Although Git includes its
647 own porcelain layer, its low-level commands are sufficient to support
648 development of alternative porcelains. Developers of such porcelains
649 might start by reading about linkgit:git-update-index[1] and
650 linkgit:git-read-tree[1].
652 The interface (input, output, set of options and the semantics)
653 to these low-level commands are meant to be a lot more stable
654 than Porcelain level commands, because these commands are
655 primarily for scripted use. The interface to Porcelain commands
656 on the other hand are subject to change in order to improve the
659 The following description divides
660 the low-level commands into commands that manipulate objects (in
661 the repository, index, and working tree), commands that interrogate and
662 compare objects, and commands that move objects and references between
666 Manipulation commands
667 ~~~~~~~~~~~~~~~~~~~~~
669 include::cmds-plumbingmanipulators.txt[]
672 Interrogation commands
673 ~~~~~~~~~~~~~~~~~~~~~~
675 include::cmds-plumbinginterrogators.txt[]
677 In general, the interrogate commands do not touch the files in
681 Synching repositories
682 ~~~~~~~~~~~~~~~~~~~~~
684 include::cmds-synchingrepositories.txt[]
686 The following are helper commands used by the above; end users
687 typically do not use them directly.
689 include::cmds-synchelpers.txt[]
692 Internal helper commands
693 ~~~~~~~~~~~~~~~~~~~~~~~~
695 These are internal helper commands used by other commands; end
696 users typically do not use them directly.
698 include::cmds-purehelpers.txt[]
701 Configuration Mechanism
702 -----------------------
704 Git uses a simple text format to store customizations that are per
705 repository and are per user. Such a configuration file may look
710 # A '#' or ';' character indicates a comment.
715 ; Don't trust file modes
720 name = "Junio C Hamano"
721 email = "gitster@pobox.com"
725 Various commands read from the configuration file and adjust
726 their operation accordingly. See linkgit:git-config[1] for a
727 list and more details about the configuration mechanism.
730 Identifier Terminology
731 ----------------------
733 Indicates the object name for any type of object.
736 Indicates a blob object name.
739 Indicates a tree object name.
742 Indicates a commit object name.
745 Indicates a tree, commit or tag object name. A
746 command that takes a <tree-ish> argument ultimately wants to
747 operate on a <tree> object but automatically dereferences
748 <commit> and <tag> objects that point at a <tree>.
751 Indicates a commit or tag object name. A
752 command that takes a <commit-ish> argument ultimately wants to
753 operate on a <commit> object but automatically dereferences
754 <tag> objects that point at a <commit>.
757 Indicates that an object type is required.
758 Currently one of: `blob`, `tree`, `commit`, or `tag`.
761 Indicates a filename - almost always relative to the
762 root of the tree structure `GIT_INDEX_FILE` describes.
766 Any Git command accepting any <object> can also use the following
770 indicates the head of the current branch.
774 (i.e. a `refs/tags/<tag>` reference).
778 (i.e. a `refs/heads/<head>` reference).
780 For a more complete list of ways to spell object names, see
781 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
784 File/Directory Structure
785 ------------------------
787 Please see the linkgit:gitrepository-layout[5] document.
789 Read linkgit:githooks[5] for more details about each hook.
791 Higher level SCMs may provide and manage additional information in the
797 Please see linkgit:gitglossary[7].
800 Environment Variables
801 ---------------------
802 Various Git commands use the following environment variables:
806 These environment variables apply to 'all' core Git commands. Nb: it
807 is worth noting that they may be used/overridden by SCMS sitting above
808 Git so take care if using a foreign front-end.
811 This environment allows the specification of an alternate
812 index file. If not specified, the default of `$GIT_DIR/index`
815 'GIT_INDEX_VERSION'::
816 This environment variable allows the specification of an index
817 version for new repositories. It won't affect existing index
818 files. By default index file version 2 or 3 is used. See
819 linkgit:git-update-index[1] for more information.
821 'GIT_OBJECT_DIRECTORY'::
822 If the object storage directory is specified via this
823 environment variable then the sha1 directories are created
824 underneath - otherwise the default `$GIT_DIR/objects`
827 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
828 Due to the immutable nature of Git objects, old objects can be
829 archived into shared, read-only directories. This variable
830 specifies a ":" separated (on Windows ";" separated) list
831 of Git object directories which can be used to search for Git
832 objects. New objects will not be written to these directories.
835 If the 'GIT_DIR' environment variable is set then it
836 specifies a path to use instead of the default `.git`
837 for the base of the repository.
838 The '--git-dir' command-line option also sets this value.
841 Set the path to the root of the working tree.
842 This can also be controlled by the '--work-tree' command-line
843 option and the core.worktree configuration variable.
846 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
847 The '--namespace' command-line option also sets this value.
849 'GIT_CEILING_DIRECTORIES'::
850 This should be a colon-separated list of absolute paths. If
851 set, it is a list of directories that Git should not chdir up
852 into while looking for a repository directory (useful for
853 excluding slow-loading network directories). It will not
854 exclude the current working directory or a GIT_DIR set on the
855 command line or in the environment. Normally, Git has to read
856 the entries in this list and resolve any symlink that
857 might be present in order to compare them with the current
858 directory. However, if even this access is slow, you
859 can add an empty entry to the list to tell Git that the
860 subsequent entries are not symlinks and needn't be resolved;
862 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
864 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
865 When run in a directory that does not have ".git" repository
866 directory, Git tries to find such a directory in the parent
867 directories to find the top of the working tree, but by default it
868 does not cross filesystem boundaries. This environment variable
869 can be set to true to tell Git not to stop at filesystem
870 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
871 an explicit repository directory set via 'GIT_DIR' or on the
875 If this variable is set to a path, non-worktree files that are
876 normally in $GIT_DIR will be taken from this path
877 instead. Worktree-specific files such as HEAD or index are
878 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
879 linkgit:git-worktree[1] for
880 details. This variable has lower precedence than other path
881 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
888 'GIT_COMMITTER_NAME'::
889 'GIT_COMMITTER_EMAIL'::
890 'GIT_COMMITTER_DATE'::
892 see linkgit:git-commit-tree[1]
897 Only valid setting is "--unified=??" or "-u??" to set the
898 number of context lines shown when a unified diff is created.
899 This takes precedence over any "-U" or "--unified" option
900 value passed on the Git diff command line.
902 'GIT_EXTERNAL_DIFF'::
903 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
904 program named by it is called, instead of the diff invocation
905 described above. For a path that is added, removed, or modified,
906 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
908 path old-file old-hex old-mode new-file new-hex new-mode
912 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
913 contents of <old|new>,
914 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
915 <old|new>-mode:: are the octal representation of the file modes.
917 The file parameters can point at the user's working file
918 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
919 when a new file is added), or a temporary file (e.g. `old-file` in the
920 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
921 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
923 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
926 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
927 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
929 'GIT_DIFF_PATH_COUNTER'::
930 A 1-based counter incremented by one for every path.
932 'GIT_DIFF_PATH_TOTAL'::
933 The total number of paths.
937 'GIT_MERGE_VERBOSITY'::
938 A number controlling the amount of output shown by
939 the recursive merge strategy. Overrides merge.verbosity.
940 See linkgit:git-merge[1]
943 This environment variable overrides `$PAGER`. If it is set
944 to an empty string or to the value "cat", Git will not launch
945 a pager. See also the `core.pager` option in
946 linkgit:git-config[1].
949 This environment variable overrides `$EDITOR` and `$VISUAL`.
950 It is used by several Git commands when, on interactive mode,
951 an editor is to be launched. See also linkgit:git-var[1]
952 and the `core.editor` option in linkgit:git-config[1].
956 If either of these environment variables is set then 'git fetch'
957 and 'git push' will use the specified command instead of 'ssh'
958 when they need to connect to a remote system.
959 The command will be given exactly two or four arguments: the
960 'username@host' (or just 'host') from the URL and the shell
961 command to execute on that remote system, optionally preceded by
962 '-p' (literally) and the 'port' from the URL when it specifies
963 something other than the default SSH port.
965 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
966 by the shell, which allows additional arguments to be included.
967 `$GIT_SSH` on the other hand must be just the path to a program
968 (which can be a wrapper shell script, if additional arguments are
971 Usually it is easier to configure any desired options through your
972 personal `.ssh/config` file. Please consult your ssh documentation
976 If this environment variable is set, then Git commands which need to
977 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
978 will call this program with a suitable prompt as command-line argument
979 and read the password from its STDOUT. See also the 'core.askPass'
980 option in linkgit:git-config[1].
982 'GIT_TERMINAL_PROMPT'::
983 If this environment variable is set to `0`, git will not prompt
984 on the terminal (e.g., when asking for HTTP authentication).
986 'GIT_CONFIG_NOSYSTEM'::
987 Whether to skip reading settings from the system-wide
988 `$(prefix)/etc/gitconfig` file. This environment variable can
989 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
990 predictable environment for a picky script, or you can set it
991 temporarily to avoid using a buggy `/etc/gitconfig` file while
992 waiting for someone with sufficient permissions to fix it.
995 If this environment variable is set to "1", then commands such
996 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
997 'git check-attr' and 'git check-ignore' will
998 force a flush of the output stream after each record have been
1000 variable is set to "0", the output of these commands will be done
1001 using completely buffered I/O. If this environment variable is
1002 not set, Git will choose buffered or record-oriented flushing
1003 based on whether stdout appears to be redirected to a file or not.
1006 Enables general trace messages, e.g. alias expansion, built-in
1007 command execution and external command execution.
1009 If this variable is set to "1", "2" or "true" (comparison
1010 is case insensitive), trace messages will be printed to
1013 If the variable is set to an integer value greater than 2
1014 and lower than 10 (strictly) then Git will interpret this
1015 value as an open file descriptor and will try to write the
1016 trace messages into this file descriptor.
1018 Alternatively, if the variable is set to an absolute path
1019 (starting with a '/' character), Git will interpret this
1020 as a file path and will try to write the trace messages
1023 Unsetting the variable, or setting it to empty, "0" or
1024 "false" (case insensitive) disables trace messages.
1026 'GIT_TRACE_PACK_ACCESS'::
1027 Enables trace messages for all accesses to any packs. For each
1028 access, the pack file name and an offset in the pack is
1029 recorded. This may be helpful for troubleshooting some
1030 pack-related performance problems.
1031 See 'GIT_TRACE' for available trace output options.
1033 'GIT_TRACE_PACKET'::
1034 Enables trace messages for all packets coming in or out of a
1035 given program. This can help with debugging object negotiation
1036 or other protocol issues. Tracing is turned off at a packet
1037 starting with "PACK" (but see 'GIT_TRACE_PACKFILE' below).
1038 See 'GIT_TRACE' for available trace output options.
1040 'GIT_TRACE_PACKFILE'::
1041 Enables tracing of packfiles sent or received by a
1042 given program. Unlike other trace output, this trace is
1043 verbatim: no headers, and no quoting of binary data. You almost
1044 certainly want to direct into a file (e.g.,
1045 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1046 the terminal or mixing it with other trace output.
1048 Note that this is currently only implemented for the client side
1049 of clones and fetches.
1051 'GIT_TRACE_PERFORMANCE'::
1052 Enables performance related trace messages, e.g. total execution
1053 time of each Git command.
1054 See 'GIT_TRACE' for available trace output options.
1057 Enables trace messages printing the .git, working tree and current
1058 working directory after Git has completed its setup phase.
1059 See 'GIT_TRACE' for available trace output options.
1061 'GIT_TRACE_SHALLOW'::
1062 Enables trace messages that can help debugging fetching /
1063 cloning of shallow repositories.
1064 See 'GIT_TRACE' for available trace output options.
1066 'GIT_LITERAL_PATHSPECS'::
1067 Setting this variable to `1` will cause Git to treat all
1068 pathspecs literally, rather than as glob patterns. For example,
1069 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1070 for commits that touch the path `*.c`, not any paths that the
1071 glob `*.c` matches. You might want this if you are feeding
1072 literal paths to Git (e.g., paths previously given to you by
1073 `git ls-tree`, `--raw` diff output, etc).
1075 'GIT_GLOB_PATHSPECS'::
1076 Setting this variable to `1` will cause Git to treat all
1077 pathspecs as glob patterns (aka "glob" magic).
1079 'GIT_NOGLOB_PATHSPECS'::
1080 Setting this variable to `1` will cause Git to treat all
1081 pathspecs as literal (aka "literal" magic).
1083 'GIT_ICASE_PATHSPECS'::
1084 Setting this variable to `1` will cause Git to treat all
1085 pathspecs as case-insensitive.
1087 'GIT_REFLOG_ACTION'::
1088 When a ref is updated, reflog entries are created to keep
1089 track of the reason why the ref was updated (which is
1090 typically the name of the high-level command that updated
1091 the ref), in addition to the old and new values of the ref.
1092 A scripted Porcelain command can use set_reflog_action
1093 helper function in `git-sh-setup` to set its name to this
1094 variable when it is invoked as the top level command by the
1095 end user, to be recorded in the body of the reflog.
1097 'GIT_REF_PARANOIA'::
1098 If set to `1`, include broken or badly named refs when iterating
1099 over lists of refs. In a normal, non-corrupted repository, this
1100 does nothing. However, enabling it may help git to detect and
1101 abort some operations in the presence of broken refs. Git sets
1102 this variable automatically when performing destructive
1103 operations like linkgit:git-prune[1]. You should not need to set
1104 it yourself unless you want to be paranoid about making sure
1105 an operation has touched every ref (e.g., because you are
1106 cloning a repository to make a backup).
1108 'GIT_ALLOW_PROTOCOL'::
1109 If set, provide a colon-separated list of protocols which are
1110 allowed to be used with fetch/push/clone. This is useful to
1111 restrict recursive submodule initialization from an untrusted
1112 repository. Any protocol not mentioned will be disallowed (i.e.,
1113 this is a whitelist, not a blacklist). If the variable is not
1114 set at all, all protocols are enabled. The protocol names
1115 currently used by git are:
1117 - `file`: any local file-based path (including `file://` URLs,
1120 - `git`: the anonymous git protocol over a direct TCP
1121 connection (or proxy, if configured)
1123 - `ssh`: git over ssh (including `host:path` syntax,
1126 - `rsync`: git over rsync
1128 - `http`: git over http, both "smart http" and "dumb http".
1129 Note that this does _not_ include `https`; if you want both,
1130 you should specify both as `http:https`.
1132 - any external helpers are named by their protocol (e.g., use
1133 `hg` to allow the `git-remote-hg` helper)
1136 Discussion[[Discussion]]
1137 ------------------------
1139 More detail on the following is available from the
1140 link:user-manual.html#git-concepts[Git concepts chapter of the
1141 user-manual] and linkgit:gitcore-tutorial[7].
1143 A Git project normally consists of a working directory with a ".git"
1144 subdirectory at the top level. The .git directory contains, among other
1145 things, a compressed object database representing the complete history
1146 of the project, an "index" file which links that history to the current
1147 contents of the working tree, and named pointers into that history such
1148 as tags and branch heads.
1150 The object database contains objects of three main types: blobs, which
1151 hold file data; trees, which point to blobs and other trees to build up
1152 directory hierarchies; and commits, which each reference a single tree
1153 and some number of parent commits.
1155 The commit, equivalent to what other systems call a "changeset" or
1156 "version", represents a step in the project's history, and each parent
1157 represents an immediately preceding step. Commits with more than one
1158 parent represent merges of independent lines of development.
1160 All objects are named by the SHA-1 hash of their contents, normally
1161 written as a string of 40 hex digits. Such names are globally unique.
1162 The entire history leading up to a commit can be vouched for by signing
1163 just that commit. A fourth object type, the tag, is provided for this
1166 When first created, objects are stored in individual files, but for
1167 efficiency may later be compressed together into "pack files".
1169 Named pointers called refs mark interesting points in history. A ref
1170 may contain the SHA-1 name of an object or the name of another ref. Refs
1171 with names beginning `ref/head/` contain the SHA-1 name of the most
1172 recent commit (or "head") of a branch under development. SHA-1 names of
1173 tags of interest are stored under `ref/tags/`. A special ref named
1174 `HEAD` contains the name of the currently checked-out branch.
1176 The index file is initialized with a list of all paths and, for each
1177 path, a blob object and a set of attributes. The blob object represents
1178 the contents of the file as of the head of the current branch. The
1179 attributes (last modified time, size, etc.) are taken from the
1180 corresponding file in the working tree. Subsequent changes to the
1181 working tree can be found by comparing these attributes. The index may
1182 be updated with new content, and new commits may be created from the
1183 content stored in the index.
1185 The index is also capable of storing multiple entries (called "stages")
1186 for a given pathname. These stages are used to hold the various
1187 unmerged version of a file when a merge is in progress.
1189 FURTHER DOCUMENTATION
1190 ---------------------
1192 See the references in the "description" section to get started
1193 using Git. The following is probably more detail than necessary
1194 for a first-time user.
1196 The link:user-manual.html#git-concepts[Git concepts chapter of the
1197 user-manual] and linkgit:gitcore-tutorial[7] both provide
1198 introductions to the underlying Git architecture.
1200 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1202 See also the link:howto-index.html[howto] documents for some useful
1205 The internals are documented in the
1206 link:technical/api-index.html[Git API documentation].
1208 Users migrating from CVS may also want to
1209 read linkgit:gitcvs-migration[7].
1214 Git was started by Linus Torvalds, and is currently maintained by Junio
1215 C Hamano. Numerous contributions have come from the Git mailing list
1216 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1217 gives you a more complete list of contributors.
1219 If you have a clone of git.git itself, the
1220 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1221 the authors for specific parts of the project.
1226 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1227 development and maintenance is primarily done. You do not have to be
1228 subscribed to the list to send a message there.
1232 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1233 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1234 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1235 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1236 linkgit:gitworkflows[7]
1240 Part of the linkgit:git[1] suite