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.3/git.html[documentation for release 2.7.3]
49 link:RelNotes/2.7.3.txt[2.7.3],
50 link:RelNotes/2.7.2.txt[2.7.2],
51 link:RelNotes/2.7.1.txt[2.7.1],
52 link:RelNotes/2.7.0.txt[2.7].
54 * link:v2.6.7/git.html[documentation for release 2.6.7]
57 link:RelNotes/2.6.7.txt[2.6.7],
58 link:RelNotes/2.6.6.txt[2.6.6],
59 link:RelNotes/2.6.5.txt[2.6.5],
60 link:RelNotes/2.6.4.txt[2.6.4],
61 link:RelNotes/2.6.3.txt[2.6.3],
62 link:RelNotes/2.6.2.txt[2.6.2],
63 link:RelNotes/2.6.1.txt[2.6.1],
64 link:RelNotes/2.6.0.txt[2.6].
66 * link:v2.5.6/git.html[documentation for release 2.5.6]
69 link:RelNotes/2.5.6.txt[2.5.6],
70 link:RelNotes/2.5.5.txt[2.5.5],
71 link:RelNotes/2.5.4.txt[2.5.4],
72 link:RelNotes/2.5.3.txt[2.5.3],
73 link:RelNotes/2.5.2.txt[2.5.2],
74 link:RelNotes/2.5.1.txt[2.5.1],
75 link:RelNotes/2.5.0.txt[2.5].
77 * link:v2.4.12/git.html[documentation for release 2.4.12]
80 link:RelNotes/2.4.12.txt[2.4.12],
81 link:RelNotes/2.4.11.txt[2.4.11],
82 link:RelNotes/2.4.10.txt[2.4.10],
83 link:RelNotes/2.4.9.txt[2.4.9],
84 link:RelNotes/2.4.8.txt[2.4.8],
85 link:RelNotes/2.4.7.txt[2.4.7],
86 link:RelNotes/2.4.6.txt[2.4.6],
87 link:RelNotes/2.4.5.txt[2.4.5],
88 link:RelNotes/2.4.4.txt[2.4.4],
89 link:RelNotes/2.4.3.txt[2.4.3],
90 link:RelNotes/2.4.2.txt[2.4.2],
91 link:RelNotes/2.4.1.txt[2.4.1],
92 link:RelNotes/2.4.0.txt[2.4].
94 * link:v2.3.10/git.html[documentation for release 2.3.10]
97 link:RelNotes/2.3.10.txt[2.3.10],
98 link:RelNotes/2.3.9.txt[2.3.9],
99 link:RelNotes/2.3.8.txt[2.3.8],
100 link:RelNotes/2.3.7.txt[2.3.7],
101 link:RelNotes/2.3.6.txt[2.3.6],
102 link:RelNotes/2.3.5.txt[2.3.5],
103 link:RelNotes/2.3.4.txt[2.3.4],
104 link:RelNotes/2.3.3.txt[2.3.3],
105 link:RelNotes/2.3.2.txt[2.3.2],
106 link:RelNotes/2.3.1.txt[2.3.1],
107 link:RelNotes/2.3.0.txt[2.3].
109 * link:v2.2.3/git.html[documentation for release 2.2.3]
112 link:RelNotes/2.2.3.txt[2.2.3],
113 link:RelNotes/2.2.2.txt[2.2.2],
114 link:RelNotes/2.2.1.txt[2.2.1],
115 link:RelNotes/2.2.0.txt[2.2].
117 * link:v2.1.4/git.html[documentation for release 2.1.4]
120 link:RelNotes/2.1.4.txt[2.1.4],
121 link:RelNotes/2.1.3.txt[2.1.3],
122 link:RelNotes/2.1.2.txt[2.1.2],
123 link:RelNotes/2.1.1.txt[2.1.1],
124 link:RelNotes/2.1.0.txt[2.1].
126 * link:v2.0.5/git.html[documentation for release 2.0.5]
129 link:RelNotes/2.0.5.txt[2.0.5],
130 link:RelNotes/2.0.4.txt[2.0.4],
131 link:RelNotes/2.0.3.txt[2.0.3],
132 link:RelNotes/2.0.2.txt[2.0.2],
133 link:RelNotes/2.0.1.txt[2.0.1],
134 link:RelNotes/2.0.0.txt[2.0.0].
136 * link:v1.9.5/git.html[documentation for release 1.9.5]
139 link:RelNotes/1.9.5.txt[1.9.5],
140 link:RelNotes/1.9.4.txt[1.9.4],
141 link:RelNotes/1.9.3.txt[1.9.3],
142 link:RelNotes/1.9.2.txt[1.9.2],
143 link:RelNotes/1.9.1.txt[1.9.1],
144 link:RelNotes/1.9.0.txt[1.9.0].
146 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
149 link:RelNotes/1.8.5.6.txt[1.8.5.6],
150 link:RelNotes/1.8.5.5.txt[1.8.5.5],
151 link:RelNotes/1.8.5.4.txt[1.8.5.4],
152 link:RelNotes/1.8.5.3.txt[1.8.5.3],
153 link:RelNotes/1.8.5.2.txt[1.8.5.2],
154 link:RelNotes/1.8.5.1.txt[1.8.5.1],
155 link:RelNotes/1.8.5.txt[1.8.5].
157 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
160 link:RelNotes/1.8.4.5.txt[1.8.4.5],
161 link:RelNotes/1.8.4.4.txt[1.8.4.4],
162 link:RelNotes/1.8.4.3.txt[1.8.4.3],
163 link:RelNotes/1.8.4.2.txt[1.8.4.2],
164 link:RelNotes/1.8.4.1.txt[1.8.4.1],
165 link:RelNotes/1.8.4.txt[1.8.4].
167 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
170 link:RelNotes/1.8.3.4.txt[1.8.3.4],
171 link:RelNotes/1.8.3.3.txt[1.8.3.3],
172 link:RelNotes/1.8.3.2.txt[1.8.3.2],
173 link:RelNotes/1.8.3.1.txt[1.8.3.1],
174 link:RelNotes/1.8.3.txt[1.8.3].
176 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
179 link:RelNotes/1.8.2.3.txt[1.8.2.3],
180 link:RelNotes/1.8.2.2.txt[1.8.2.2],
181 link:RelNotes/1.8.2.1.txt[1.8.2.1],
182 link:RelNotes/1.8.2.txt[1.8.2].
184 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
187 link:RelNotes/1.8.1.6.txt[1.8.1.6],
188 link:RelNotes/1.8.1.5.txt[1.8.1.5],
189 link:RelNotes/1.8.1.4.txt[1.8.1.4],
190 link:RelNotes/1.8.1.3.txt[1.8.1.3],
191 link:RelNotes/1.8.1.2.txt[1.8.1.2],
192 link:RelNotes/1.8.1.1.txt[1.8.1.1],
193 link:RelNotes/1.8.1.txt[1.8.1].
195 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
198 link:RelNotes/1.8.0.3.txt[1.8.0.3],
199 link:RelNotes/1.8.0.2.txt[1.8.0.2],
200 link:RelNotes/1.8.0.1.txt[1.8.0.1],
201 link:RelNotes/1.8.0.txt[1.8.0].
203 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
206 link:RelNotes/1.7.12.4.txt[1.7.12.4],
207 link:RelNotes/1.7.12.3.txt[1.7.12.3],
208 link:RelNotes/1.7.12.2.txt[1.7.12.2],
209 link:RelNotes/1.7.12.1.txt[1.7.12.1],
210 link:RelNotes/1.7.12.txt[1.7.12].
212 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
215 link:RelNotes/1.7.11.7.txt[1.7.11.7],
216 link:RelNotes/1.7.11.6.txt[1.7.11.6],
217 link:RelNotes/1.7.11.5.txt[1.7.11.5],
218 link:RelNotes/1.7.11.4.txt[1.7.11.4],
219 link:RelNotes/1.7.11.3.txt[1.7.11.3],
220 link:RelNotes/1.7.11.2.txt[1.7.11.2],
221 link:RelNotes/1.7.11.1.txt[1.7.11.1],
222 link:RelNotes/1.7.11.txt[1.7.11].
224 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
227 link:RelNotes/1.7.10.5.txt[1.7.10.5],
228 link:RelNotes/1.7.10.4.txt[1.7.10.4],
229 link:RelNotes/1.7.10.3.txt[1.7.10.3],
230 link:RelNotes/1.7.10.2.txt[1.7.10.2],
231 link:RelNotes/1.7.10.1.txt[1.7.10.1],
232 link:RelNotes/1.7.10.txt[1.7.10].
234 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
237 link:RelNotes/1.7.9.7.txt[1.7.9.7],
238 link:RelNotes/1.7.9.6.txt[1.7.9.6],
239 link:RelNotes/1.7.9.5.txt[1.7.9.5],
240 link:RelNotes/1.7.9.4.txt[1.7.9.4],
241 link:RelNotes/1.7.9.3.txt[1.7.9.3],
242 link:RelNotes/1.7.9.2.txt[1.7.9.2],
243 link:RelNotes/1.7.9.1.txt[1.7.9.1],
244 link:RelNotes/1.7.9.txt[1.7.9].
246 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
249 link:RelNotes/1.7.8.6.txt[1.7.8.6],
250 link:RelNotes/1.7.8.5.txt[1.7.8.5],
251 link:RelNotes/1.7.8.4.txt[1.7.8.4],
252 link:RelNotes/1.7.8.3.txt[1.7.8.3],
253 link:RelNotes/1.7.8.2.txt[1.7.8.2],
254 link:RelNotes/1.7.8.1.txt[1.7.8.1],
255 link:RelNotes/1.7.8.txt[1.7.8].
257 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
260 link:RelNotes/1.7.7.7.txt[1.7.7.7],
261 link:RelNotes/1.7.7.6.txt[1.7.7.6],
262 link:RelNotes/1.7.7.5.txt[1.7.7.5],
263 link:RelNotes/1.7.7.4.txt[1.7.7.4],
264 link:RelNotes/1.7.7.3.txt[1.7.7.3],
265 link:RelNotes/1.7.7.2.txt[1.7.7.2],
266 link:RelNotes/1.7.7.1.txt[1.7.7.1],
267 link:RelNotes/1.7.7.txt[1.7.7].
269 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
272 link:RelNotes/1.7.6.6.txt[1.7.6.6],
273 link:RelNotes/1.7.6.5.txt[1.7.6.5],
274 link:RelNotes/1.7.6.4.txt[1.7.6.4],
275 link:RelNotes/1.7.6.3.txt[1.7.6.3],
276 link:RelNotes/1.7.6.2.txt[1.7.6.2],
277 link:RelNotes/1.7.6.1.txt[1.7.6.1],
278 link:RelNotes/1.7.6.txt[1.7.6].
280 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
283 link:RelNotes/1.7.5.4.txt[1.7.5.4],
284 link:RelNotes/1.7.5.3.txt[1.7.5.3],
285 link:RelNotes/1.7.5.2.txt[1.7.5.2],
286 link:RelNotes/1.7.5.1.txt[1.7.5.1],
287 link:RelNotes/1.7.5.txt[1.7.5].
289 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
292 link:RelNotes/1.7.4.5.txt[1.7.4.5],
293 link:RelNotes/1.7.4.4.txt[1.7.4.4],
294 link:RelNotes/1.7.4.3.txt[1.7.4.3],
295 link:RelNotes/1.7.4.2.txt[1.7.4.2],
296 link:RelNotes/1.7.4.1.txt[1.7.4.1],
297 link:RelNotes/1.7.4.txt[1.7.4].
299 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
302 link:RelNotes/1.7.3.5.txt[1.7.3.5],
303 link:RelNotes/1.7.3.4.txt[1.7.3.4],
304 link:RelNotes/1.7.3.3.txt[1.7.3.3],
305 link:RelNotes/1.7.3.2.txt[1.7.3.2],
306 link:RelNotes/1.7.3.1.txt[1.7.3.1],
307 link:RelNotes/1.7.3.txt[1.7.3].
309 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
312 link:RelNotes/1.7.2.5.txt[1.7.2.5],
313 link:RelNotes/1.7.2.4.txt[1.7.2.4],
314 link:RelNotes/1.7.2.3.txt[1.7.2.3],
315 link:RelNotes/1.7.2.2.txt[1.7.2.2],
316 link:RelNotes/1.7.2.1.txt[1.7.2.1],
317 link:RelNotes/1.7.2.txt[1.7.2].
319 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
322 link:RelNotes/1.7.1.4.txt[1.7.1.4],
323 link:RelNotes/1.7.1.3.txt[1.7.1.3],
324 link:RelNotes/1.7.1.2.txt[1.7.1.2],
325 link:RelNotes/1.7.1.1.txt[1.7.1.1],
326 link:RelNotes/1.7.1.txt[1.7.1].
328 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
331 link:RelNotes/1.7.0.9.txt[1.7.0.9],
332 link:RelNotes/1.7.0.8.txt[1.7.0.8],
333 link:RelNotes/1.7.0.7.txt[1.7.0.7],
334 link:RelNotes/1.7.0.6.txt[1.7.0.6],
335 link:RelNotes/1.7.0.5.txt[1.7.0.5],
336 link:RelNotes/1.7.0.4.txt[1.7.0.4],
337 link:RelNotes/1.7.0.3.txt[1.7.0.3],
338 link:RelNotes/1.7.0.2.txt[1.7.0.2],
339 link:RelNotes/1.7.0.1.txt[1.7.0.1],
340 link:RelNotes/1.7.0.txt[1.7.0].
342 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
345 link:RelNotes/1.6.6.3.txt[1.6.6.3],
346 link:RelNotes/1.6.6.2.txt[1.6.6.2],
347 link:RelNotes/1.6.6.1.txt[1.6.6.1],
348 link:RelNotes/1.6.6.txt[1.6.6].
350 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
353 link:RelNotes/1.6.5.9.txt[1.6.5.9],
354 link:RelNotes/1.6.5.8.txt[1.6.5.8],
355 link:RelNotes/1.6.5.7.txt[1.6.5.7],
356 link:RelNotes/1.6.5.6.txt[1.6.5.6],
357 link:RelNotes/1.6.5.5.txt[1.6.5.5],
358 link:RelNotes/1.6.5.4.txt[1.6.5.4],
359 link:RelNotes/1.6.5.3.txt[1.6.5.3],
360 link:RelNotes/1.6.5.2.txt[1.6.5.2],
361 link:RelNotes/1.6.5.1.txt[1.6.5.1],
362 link:RelNotes/1.6.5.txt[1.6.5].
364 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
367 link:RelNotes/1.6.4.5.txt[1.6.4.5],
368 link:RelNotes/1.6.4.4.txt[1.6.4.4],
369 link:RelNotes/1.6.4.3.txt[1.6.4.3],
370 link:RelNotes/1.6.4.2.txt[1.6.4.2],
371 link:RelNotes/1.6.4.1.txt[1.6.4.1],
372 link:RelNotes/1.6.4.txt[1.6.4].
374 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
377 link:RelNotes/1.6.3.4.txt[1.6.3.4],
378 link:RelNotes/1.6.3.3.txt[1.6.3.3],
379 link:RelNotes/1.6.3.2.txt[1.6.3.2],
380 link:RelNotes/1.6.3.1.txt[1.6.3.1],
381 link:RelNotes/1.6.3.txt[1.6.3].
384 link:RelNotes/1.6.2.5.txt[1.6.2.5],
385 link:RelNotes/1.6.2.4.txt[1.6.2.4],
386 link:RelNotes/1.6.2.3.txt[1.6.2.3],
387 link:RelNotes/1.6.2.2.txt[1.6.2.2],
388 link:RelNotes/1.6.2.1.txt[1.6.2.1],
389 link:RelNotes/1.6.2.txt[1.6.2].
391 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
394 link:RelNotes/1.6.1.3.txt[1.6.1.3],
395 link:RelNotes/1.6.1.2.txt[1.6.1.2],
396 link:RelNotes/1.6.1.1.txt[1.6.1.1],
397 link:RelNotes/1.6.1.txt[1.6.1].
399 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
402 link:RelNotes/1.6.0.6.txt[1.6.0.6],
403 link:RelNotes/1.6.0.5.txt[1.6.0.5],
404 link:RelNotes/1.6.0.4.txt[1.6.0.4],
405 link:RelNotes/1.6.0.3.txt[1.6.0.3],
406 link:RelNotes/1.6.0.2.txt[1.6.0.2],
407 link:RelNotes/1.6.0.1.txt[1.6.0.1],
408 link:RelNotes/1.6.0.txt[1.6.0].
410 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
413 link:RelNotes/1.5.6.6.txt[1.5.6.6],
414 link:RelNotes/1.5.6.5.txt[1.5.6.5],
415 link:RelNotes/1.5.6.4.txt[1.5.6.4],
416 link:RelNotes/1.5.6.3.txt[1.5.6.3],
417 link:RelNotes/1.5.6.2.txt[1.5.6.2],
418 link:RelNotes/1.5.6.1.txt[1.5.6.1],
419 link:RelNotes/1.5.6.txt[1.5.6].
421 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
424 link:RelNotes/1.5.5.6.txt[1.5.5.6],
425 link:RelNotes/1.5.5.5.txt[1.5.5.5],
426 link:RelNotes/1.5.5.4.txt[1.5.5.4],
427 link:RelNotes/1.5.5.3.txt[1.5.5.3],
428 link:RelNotes/1.5.5.2.txt[1.5.5.2],
429 link:RelNotes/1.5.5.1.txt[1.5.5.1],
430 link:RelNotes/1.5.5.txt[1.5.5].
432 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
435 link:RelNotes/1.5.4.7.txt[1.5.4.7],
436 link:RelNotes/1.5.4.6.txt[1.5.4.6],
437 link:RelNotes/1.5.4.5.txt[1.5.4.5],
438 link:RelNotes/1.5.4.4.txt[1.5.4.4],
439 link:RelNotes/1.5.4.3.txt[1.5.4.3],
440 link:RelNotes/1.5.4.2.txt[1.5.4.2],
441 link:RelNotes/1.5.4.1.txt[1.5.4.1],
442 link:RelNotes/1.5.4.txt[1.5.4].
444 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
447 link:RelNotes/1.5.3.8.txt[1.5.3.8],
448 link:RelNotes/1.5.3.7.txt[1.5.3.7],
449 link:RelNotes/1.5.3.6.txt[1.5.3.6],
450 link:RelNotes/1.5.3.5.txt[1.5.3.5],
451 link:RelNotes/1.5.3.4.txt[1.5.3.4],
452 link:RelNotes/1.5.3.3.txt[1.5.3.3],
453 link:RelNotes/1.5.3.2.txt[1.5.3.2],
454 link:RelNotes/1.5.3.1.txt[1.5.3.1],
455 link:RelNotes/1.5.3.txt[1.5.3].
457 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
460 link:RelNotes/1.5.2.5.txt[1.5.2.5],
461 link:RelNotes/1.5.2.4.txt[1.5.2.4],
462 link:RelNotes/1.5.2.3.txt[1.5.2.3],
463 link:RelNotes/1.5.2.2.txt[1.5.2.2],
464 link:RelNotes/1.5.2.1.txt[1.5.2.1],
465 link:RelNotes/1.5.2.txt[1.5.2].
467 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
470 link:RelNotes/1.5.1.6.txt[1.5.1.6],
471 link:RelNotes/1.5.1.5.txt[1.5.1.5],
472 link:RelNotes/1.5.1.4.txt[1.5.1.4],
473 link:RelNotes/1.5.1.3.txt[1.5.1.3],
474 link:RelNotes/1.5.1.2.txt[1.5.1.2],
475 link:RelNotes/1.5.1.1.txt[1.5.1.1],
476 link:RelNotes/1.5.1.txt[1.5.1].
478 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
481 link:RelNotes/1.5.0.7.txt[1.5.0.7],
482 link:RelNotes/1.5.0.6.txt[1.5.0.6],
483 link:RelNotes/1.5.0.5.txt[1.5.0.5],
484 link:RelNotes/1.5.0.3.txt[1.5.0.3],
485 link:RelNotes/1.5.0.2.txt[1.5.0.2],
486 link:RelNotes/1.5.0.1.txt[1.5.0.1],
487 link:RelNotes/1.5.0.txt[1.5.0].
489 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
490 link:v1.3.3/git.html[1.3.3],
491 link:v1.2.6/git.html[1.2.6],
492 link:v1.0.13/git.html[1.0.13].
501 Prints the Git suite version that the 'git' program came from.
504 Prints the synopsis and a list of the most commonly used
505 commands. If the option '--all' or '-a' is given then all
506 available commands are printed. If a Git command is named this
507 option will bring up the manual page for that command.
509 Other options are available to control how the manual page is
510 displayed. See linkgit:git-help[1] for more information,
511 because `git --help ...` is converted internally into `git
515 Run as if git was started in '<path>' instead of the current working
516 directory. When multiple `-C` options are given, each subsequent
517 non-absolute `-C <path>` is interpreted relative to the preceding `-C
520 This option affects options that expect path name like `--git-dir` and
521 `--work-tree` in that their interpretations of the path names would be
522 made relative to the working directory caused by the `-C` option. For
523 example the following invocations are equivalent:
525 git --git-dir=a.git --work-tree=b -C c status
526 git --git-dir=c/a.git --work-tree=c/b status
529 Pass a configuration parameter to the command. The value
530 given will override values from configuration files.
531 The <name> is expected in the same format as listed by
532 'git config' (subkeys separated by dots).
534 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
535 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
536 config file). Including the equals but with an empty value (like `git -c
537 foo.bar= ...`) sets `foo.bar` to the empty string.
539 --exec-path[=<path>]::
540 Path to wherever your core Git programs are installed.
541 This can also be controlled by setting the GIT_EXEC_PATH
542 environment variable. If no path is given, 'git' will print
543 the current setting and then exit.
546 Print the path, without trailing slash, where Git's HTML
547 documentation is installed and exit.
550 Print the manpath (see `man(1)`) for the man pages for
551 this version of Git and exit.
554 Print the path where the Info files documenting this
555 version of Git are installed and exit.
559 Pipe all output into 'less' (or if set, $PAGER) if standard
560 output is a terminal. This overrides the `pager.<cmd>`
561 configuration options (see the "Configuration Mechanism" section
565 Do not pipe Git output into a pager.
568 Set the path to the repository. This can also be controlled by
569 setting the GIT_DIR environment variable. It can be an absolute
570 path or relative path to current working directory.
573 Set the path to the working tree. It can be an absolute path
574 or a path relative to the current working directory.
575 This can also be controlled by setting the GIT_WORK_TREE
576 environment variable and the core.worktree configuration
577 variable (see core.worktree in linkgit:git-config[1] for a
578 more detailed discussion).
581 Set the Git namespace. See linkgit:gitnamespaces[7] for more
582 details. Equivalent to setting the `GIT_NAMESPACE` environment
586 Treat the repository as a bare repository. If GIT_DIR
587 environment is not set, it is set to the current working
590 --no-replace-objects::
591 Do not use replacement refs to replace Git objects. See
592 linkgit:git-replace[1] for more information.
594 --literal-pathspecs::
595 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
596 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
600 Add "glob" magic to all pathspec. This is equivalent to setting
601 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
602 globbing on individual pathspecs can be done using pathspec
606 Add "literal" magic to all pathspec. This is equivalent to setting
607 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
608 globbing on individual pathspecs can be done using pathspec
612 Add "icase" magic to all pathspec. This is equivalent to setting
613 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
618 We divide Git into high level ("porcelain") commands and low level
619 ("plumbing") commands.
621 High-level commands (porcelain)
622 -------------------------------
624 We separate the porcelain commands into the main commands and some
625 ancillary user utilities.
627 Main porcelain commands
628 ~~~~~~~~~~~~~~~~~~~~~~~
630 include::cmds-mainporcelain.txt[]
636 include::cmds-ancillarymanipulators.txt[]
640 include::cmds-ancillaryinterrogators.txt[]
643 Interacting with Others
644 ~~~~~~~~~~~~~~~~~~~~~~~
646 These commands are to interact with foreign SCM and with other
647 people via patch over e-mail.
649 include::cmds-foreignscminterface.txt[]
652 Low-level commands (plumbing)
653 -----------------------------
655 Although Git includes its
656 own porcelain layer, its low-level commands are sufficient to support
657 development of alternative porcelains. Developers of such porcelains
658 might start by reading about linkgit:git-update-index[1] and
659 linkgit:git-read-tree[1].
661 The interface (input, output, set of options and the semantics)
662 to these low-level commands are meant to be a lot more stable
663 than Porcelain level commands, because these commands are
664 primarily for scripted use. The interface to Porcelain commands
665 on the other hand are subject to change in order to improve the
668 The following description divides
669 the low-level commands into commands that manipulate objects (in
670 the repository, index, and working tree), commands that interrogate and
671 compare objects, and commands that move objects and references between
675 Manipulation commands
676 ~~~~~~~~~~~~~~~~~~~~~
678 include::cmds-plumbingmanipulators.txt[]
681 Interrogation commands
682 ~~~~~~~~~~~~~~~~~~~~~~
684 include::cmds-plumbinginterrogators.txt[]
686 In general, the interrogate commands do not touch the files in
690 Synching repositories
691 ~~~~~~~~~~~~~~~~~~~~~
693 include::cmds-synchingrepositories.txt[]
695 The following are helper commands used by the above; end users
696 typically do not use them directly.
698 include::cmds-synchelpers.txt[]
701 Internal helper commands
702 ~~~~~~~~~~~~~~~~~~~~~~~~
704 These are internal helper commands used by other commands; end
705 users typically do not use them directly.
707 include::cmds-purehelpers.txt[]
710 Configuration Mechanism
711 -----------------------
713 Git uses a simple text format to store customizations that are per
714 repository and are per user. Such a configuration file may look
719 # A '#' or ';' character indicates a comment.
724 ; Don't trust file modes
729 name = "Junio C Hamano"
730 email = "gitster@pobox.com"
734 Various commands read from the configuration file and adjust
735 their operation accordingly. See linkgit:git-config[1] for a
736 list and more details about the configuration mechanism.
739 Identifier Terminology
740 ----------------------
742 Indicates the object name for any type of object.
745 Indicates a blob object name.
748 Indicates a tree object name.
751 Indicates a commit object name.
754 Indicates a tree, commit or tag object name. A
755 command that takes a <tree-ish> argument ultimately wants to
756 operate on a <tree> object but automatically dereferences
757 <commit> and <tag> objects that point at a <tree>.
760 Indicates a commit or tag object name. A
761 command that takes a <commit-ish> argument ultimately wants to
762 operate on a <commit> object but automatically dereferences
763 <tag> objects that point at a <commit>.
766 Indicates that an object type is required.
767 Currently one of: `blob`, `tree`, `commit`, or `tag`.
770 Indicates a filename - almost always relative to the
771 root of the tree structure `GIT_INDEX_FILE` describes.
775 Any Git command accepting any <object> can also use the following
779 indicates the head of the current branch.
783 (i.e. a `refs/tags/<tag>` reference).
787 (i.e. a `refs/heads/<head>` reference).
789 For a more complete list of ways to spell object names, see
790 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
793 File/Directory Structure
794 ------------------------
796 Please see the linkgit:gitrepository-layout[5] document.
798 Read linkgit:githooks[5] for more details about each hook.
800 Higher level SCMs may provide and manage additional information in the
806 Please see linkgit:gitglossary[7].
809 Environment Variables
810 ---------------------
811 Various Git commands use the following environment variables:
815 These environment variables apply to 'all' core Git commands. Nb: it
816 is worth noting that they may be used/overridden by SCMS sitting above
817 Git so take care if using a foreign front-end.
820 This environment allows the specification of an alternate
821 index file. If not specified, the default of `$GIT_DIR/index`
824 'GIT_INDEX_VERSION'::
825 This environment variable allows the specification of an index
826 version for new repositories. It won't affect existing index
827 files. By default index file version 2 or 3 is used. See
828 linkgit:git-update-index[1] for more information.
830 'GIT_OBJECT_DIRECTORY'::
831 If the object storage directory is specified via this
832 environment variable then the sha1 directories are created
833 underneath - otherwise the default `$GIT_DIR/objects`
836 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
837 Due to the immutable nature of Git objects, old objects can be
838 archived into shared, read-only directories. This variable
839 specifies a ":" separated (on Windows ";" separated) list
840 of Git object directories which can be used to search for Git
841 objects. New objects will not be written to these directories.
844 If the 'GIT_DIR' environment variable is set then it
845 specifies a path to use instead of the default `.git`
846 for the base of the repository.
847 The '--git-dir' command-line option also sets this value.
850 Set the path to the root of the working tree.
851 This can also be controlled by the '--work-tree' command-line
852 option and the core.worktree configuration variable.
855 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
856 The '--namespace' command-line option also sets this value.
858 'GIT_CEILING_DIRECTORIES'::
859 This should be a colon-separated list of absolute paths. If
860 set, it is a list of directories that Git should not chdir up
861 into while looking for a repository directory (useful for
862 excluding slow-loading network directories). It will not
863 exclude the current working directory or a GIT_DIR set on the
864 command line or in the environment. Normally, Git has to read
865 the entries in this list and resolve any symlink that
866 might be present in order to compare them with the current
867 directory. However, if even this access is slow, you
868 can add an empty entry to the list to tell Git that the
869 subsequent entries are not symlinks and needn't be resolved;
871 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
873 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
874 When run in a directory that does not have ".git" repository
875 directory, Git tries to find such a directory in the parent
876 directories to find the top of the working tree, but by default it
877 does not cross filesystem boundaries. This environment variable
878 can be set to true to tell Git not to stop at filesystem
879 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
880 an explicit repository directory set via 'GIT_DIR' or on the
884 If this variable is set to a path, non-worktree files that are
885 normally in $GIT_DIR will be taken from this path
886 instead. Worktree-specific files such as HEAD or index are
887 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
888 linkgit:git-worktree[1] for
889 details. This variable has lower precedence than other path
890 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
897 'GIT_COMMITTER_NAME'::
898 'GIT_COMMITTER_EMAIL'::
899 'GIT_COMMITTER_DATE'::
901 see linkgit:git-commit-tree[1]
906 Only valid setting is "--unified=??" or "-u??" to set the
907 number of context lines shown when a unified diff is created.
908 This takes precedence over any "-U" or "--unified" option
909 value passed on the Git diff command line.
911 'GIT_EXTERNAL_DIFF'::
912 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
913 program named by it is called, instead of the diff invocation
914 described above. For a path that is added, removed, or modified,
915 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
917 path old-file old-hex old-mode new-file new-hex new-mode
921 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
922 contents of <old|new>,
923 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
924 <old|new>-mode:: are the octal representation of the file modes.
926 The file parameters can point at the user's working file
927 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
928 when a new file is added), or a temporary file (e.g. `old-file` in the
929 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
930 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
932 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
935 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
936 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
938 'GIT_DIFF_PATH_COUNTER'::
939 A 1-based counter incremented by one for every path.
941 'GIT_DIFF_PATH_TOTAL'::
942 The total number of paths.
946 'GIT_MERGE_VERBOSITY'::
947 A number controlling the amount of output shown by
948 the recursive merge strategy. Overrides merge.verbosity.
949 See linkgit:git-merge[1]
952 This environment variable overrides `$PAGER`. If it is set
953 to an empty string or to the value "cat", Git will not launch
954 a pager. See also the `core.pager` option in
955 linkgit:git-config[1].
958 This environment variable overrides `$EDITOR` and `$VISUAL`.
959 It is used by several Git commands when, on interactive mode,
960 an editor is to be launched. See also linkgit:git-var[1]
961 and the `core.editor` option in linkgit:git-config[1].
965 If either of these environment variables is set then 'git fetch'
966 and 'git push' will use the specified command instead of 'ssh'
967 when they need to connect to a remote system.
968 The command will be given exactly two or four arguments: the
969 'username@host' (or just 'host') from the URL and the shell
970 command to execute on that remote system, optionally preceded by
971 '-p' (literally) and the 'port' from the URL when it specifies
972 something other than the default SSH port.
974 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
975 by the shell, which allows additional arguments to be included.
976 `$GIT_SSH` on the other hand must be just the path to a program
977 (which can be a wrapper shell script, if additional arguments are
980 Usually it is easier to configure any desired options through your
981 personal `.ssh/config` file. Please consult your ssh documentation
985 If this environment variable is set, then Git commands which need to
986 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
987 will call this program with a suitable prompt as command-line argument
988 and read the password from its STDOUT. See also the 'core.askPass'
989 option in linkgit:git-config[1].
991 'GIT_TERMINAL_PROMPT'::
992 If this environment variable is set to `0`, git will not prompt
993 on the terminal (e.g., when asking for HTTP authentication).
995 'GIT_CONFIG_NOSYSTEM'::
996 Whether to skip reading settings from the system-wide
997 `$(prefix)/etc/gitconfig` file. This environment variable can
998 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
999 predictable environment for a picky script, or you can set it
1000 temporarily to avoid using a buggy `/etc/gitconfig` file while
1001 waiting for someone with sufficient permissions to fix it.
1004 If this environment variable is set to "1", then commands such
1005 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
1006 'git check-attr' and 'git check-ignore' will
1007 force a flush of the output stream after each record have been
1009 variable is set to "0", the output of these commands will be done
1010 using completely buffered I/O. If this environment variable is
1011 not set, Git will choose buffered or record-oriented flushing
1012 based on whether stdout appears to be redirected to a file or not.
1015 Enables general trace messages, e.g. alias expansion, built-in
1016 command execution and external command execution.
1018 If this variable is set to "1", "2" or "true" (comparison
1019 is case insensitive), trace messages will be printed to
1022 If the variable is set to an integer value greater than 2
1023 and lower than 10 (strictly) then Git will interpret this
1024 value as an open file descriptor and will try to write the
1025 trace messages into this file descriptor.
1027 Alternatively, if the variable is set to an absolute path
1028 (starting with a '/' character), Git will interpret this
1029 as a file path and will try to write the trace messages
1032 Unsetting the variable, or setting it to empty, "0" or
1033 "false" (case insensitive) disables trace messages.
1035 'GIT_TRACE_PACK_ACCESS'::
1036 Enables trace messages for all accesses to any packs. For each
1037 access, the pack file name and an offset in the pack is
1038 recorded. This may be helpful for troubleshooting some
1039 pack-related performance problems.
1040 See 'GIT_TRACE' for available trace output options.
1042 'GIT_TRACE_PACKET'::
1043 Enables trace messages for all packets coming in or out of a
1044 given program. This can help with debugging object negotiation
1045 or other protocol issues. Tracing is turned off at a packet
1046 starting with "PACK" (but see 'GIT_TRACE_PACKFILE' below).
1047 See 'GIT_TRACE' for available trace output options.
1049 'GIT_TRACE_PACKFILE'::
1050 Enables tracing of packfiles sent or received by a
1051 given program. Unlike other trace output, this trace is
1052 verbatim: no headers, and no quoting of binary data. You almost
1053 certainly want to direct into a file (e.g.,
1054 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1055 the terminal or mixing it with other trace output.
1057 Note that this is currently only implemented for the client side
1058 of clones and fetches.
1060 'GIT_TRACE_PERFORMANCE'::
1061 Enables performance related trace messages, e.g. total execution
1062 time of each Git command.
1063 See 'GIT_TRACE' for available trace output options.
1066 Enables trace messages printing the .git, working tree and current
1067 working directory after Git has completed its setup phase.
1068 See 'GIT_TRACE' for available trace output options.
1070 'GIT_TRACE_SHALLOW'::
1071 Enables trace messages that can help debugging fetching /
1072 cloning of shallow repositories.
1073 See 'GIT_TRACE' for available trace output options.
1075 'GIT_LITERAL_PATHSPECS'::
1076 Setting this variable to `1` will cause Git to treat all
1077 pathspecs literally, rather than as glob patterns. For example,
1078 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1079 for commits that touch the path `*.c`, not any paths that the
1080 glob `*.c` matches. You might want this if you are feeding
1081 literal paths to Git (e.g., paths previously given to you by
1082 `git ls-tree`, `--raw` diff output, etc).
1084 'GIT_GLOB_PATHSPECS'::
1085 Setting this variable to `1` will cause Git to treat all
1086 pathspecs as glob patterns (aka "glob" magic).
1088 'GIT_NOGLOB_PATHSPECS'::
1089 Setting this variable to `1` will cause Git to treat all
1090 pathspecs as literal (aka "literal" magic).
1092 'GIT_ICASE_PATHSPECS'::
1093 Setting this variable to `1` will cause Git to treat all
1094 pathspecs as case-insensitive.
1096 'GIT_REFLOG_ACTION'::
1097 When a ref is updated, reflog entries are created to keep
1098 track of the reason why the ref was updated (which is
1099 typically the name of the high-level command that updated
1100 the ref), in addition to the old and new values of the ref.
1101 A scripted Porcelain command can use set_reflog_action
1102 helper function in `git-sh-setup` to set its name to this
1103 variable when it is invoked as the top level command by the
1104 end user, to be recorded in the body of the reflog.
1106 'GIT_REF_PARANOIA'::
1107 If set to `1`, include broken or badly named refs when iterating
1108 over lists of refs. In a normal, non-corrupted repository, this
1109 does nothing. However, enabling it may help git to detect and
1110 abort some operations in the presence of broken refs. Git sets
1111 this variable automatically when performing destructive
1112 operations like linkgit:git-prune[1]. You should not need to set
1113 it yourself unless you want to be paranoid about making sure
1114 an operation has touched every ref (e.g., because you are
1115 cloning a repository to make a backup).
1117 'GIT_ALLOW_PROTOCOL'::
1118 If set, provide a colon-separated list of protocols which are
1119 allowed to be used with fetch/push/clone. This is useful to
1120 restrict recursive submodule initialization from an untrusted
1121 repository. Any protocol not mentioned will be disallowed (i.e.,
1122 this is a whitelist, not a blacklist). If the variable is not
1123 set at all, all protocols are enabled. The protocol names
1124 currently used by git are:
1126 - `file`: any local file-based path (including `file://` URLs,
1129 - `git`: the anonymous git protocol over a direct TCP
1130 connection (or proxy, if configured)
1132 - `ssh`: git over ssh (including `host:path` syntax,
1135 - `rsync`: git over rsync
1137 - `http`: git over http, both "smart http" and "dumb http".
1138 Note that this does _not_ include `https`; if you want both,
1139 you should specify both as `http:https`.
1141 - any external helpers are named by their protocol (e.g., use
1142 `hg` to allow the `git-remote-hg` helper)
1145 Discussion[[Discussion]]
1146 ------------------------
1148 More detail on the following is available from the
1149 link:user-manual.html#git-concepts[Git concepts chapter of the
1150 user-manual] and linkgit:gitcore-tutorial[7].
1152 A Git project normally consists of a working directory with a ".git"
1153 subdirectory at the top level. The .git directory contains, among other
1154 things, a compressed object database representing the complete history
1155 of the project, an "index" file which links that history to the current
1156 contents of the working tree, and named pointers into that history such
1157 as tags and branch heads.
1159 The object database contains objects of three main types: blobs, which
1160 hold file data; trees, which point to blobs and other trees to build up
1161 directory hierarchies; and commits, which each reference a single tree
1162 and some number of parent commits.
1164 The commit, equivalent to what other systems call a "changeset" or
1165 "version", represents a step in the project's history, and each parent
1166 represents an immediately preceding step. Commits with more than one
1167 parent represent merges of independent lines of development.
1169 All objects are named by the SHA-1 hash of their contents, normally
1170 written as a string of 40 hex digits. Such names are globally unique.
1171 The entire history leading up to a commit can be vouched for by signing
1172 just that commit. A fourth object type, the tag, is provided for this
1175 When first created, objects are stored in individual files, but for
1176 efficiency may later be compressed together into "pack files".
1178 Named pointers called refs mark interesting points in history. A ref
1179 may contain the SHA-1 name of an object or the name of another ref. Refs
1180 with names beginning `ref/head/` contain the SHA-1 name of the most
1181 recent commit (or "head") of a branch under development. SHA-1 names of
1182 tags of interest are stored under `ref/tags/`. A special ref named
1183 `HEAD` contains the name of the currently checked-out branch.
1185 The index file is initialized with a list of all paths and, for each
1186 path, a blob object and a set of attributes. The blob object represents
1187 the contents of the file as of the head of the current branch. The
1188 attributes (last modified time, size, etc.) are taken from the
1189 corresponding file in the working tree. Subsequent changes to the
1190 working tree can be found by comparing these attributes. The index may
1191 be updated with new content, and new commits may be created from the
1192 content stored in the index.
1194 The index is also capable of storing multiple entries (called "stages")
1195 for a given pathname. These stages are used to hold the various
1196 unmerged version of a file when a merge is in progress.
1198 FURTHER DOCUMENTATION
1199 ---------------------
1201 See the references in the "description" section to get started
1202 using Git. The following is probably more detail than necessary
1203 for a first-time user.
1205 The link:user-manual.html#git-concepts[Git concepts chapter of the
1206 user-manual] and linkgit:gitcore-tutorial[7] both provide
1207 introductions to the underlying Git architecture.
1209 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1211 See also the link:howto-index.html[howto] documents for some useful
1214 The internals are documented in the
1215 link:technical/api-index.html[Git API documentation].
1217 Users migrating from CVS may also want to
1218 read linkgit:gitcvs-migration[7].
1223 Git was started by Linus Torvalds, and is currently maintained by Junio
1224 C Hamano. Numerous contributions have come from the Git mailing list
1225 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1226 gives you a more complete list of contributors.
1228 If you have a clone of git.git itself, the
1229 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1230 the authors for specific parts of the project.
1235 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1236 development and maintenance is primarily done. You do not have to be
1237 subscribed to the list to send a message there.
1241 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1242 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1243 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1244 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1245 linkgit:gitworkflows[7]
1249 Part of the linkgit:git[1] suite