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.6.0/git.html[documentation for release 2.6]
49 link:RelNotes/2.6.0.txt[2.6].
51 * link:v2.5.3/git.html[documentation for release 2.5.3]
54 link:RelNotes/2.5.3.txt[2.5.3],
55 link:RelNotes/2.5.2.txt[2.5.2],
56 link:RelNotes/2.5.1.txt[2.5.1],
57 link:RelNotes/2.5.0.txt[2.5].
59 * link:v2.4.9/git.html[documentation for release 2.4.9]
62 link:RelNotes/2.4.9.txt[2.4.9],
63 link:RelNotes/2.4.8.txt[2.4.8],
64 link:RelNotes/2.4.7.txt[2.4.7],
65 link:RelNotes/2.4.6.txt[2.4.6],
66 link:RelNotes/2.4.5.txt[2.4.5],
67 link:RelNotes/2.4.4.txt[2.4.4],
68 link:RelNotes/2.4.3.txt[2.4.3],
69 link:RelNotes/2.4.2.txt[2.4.2],
70 link:RelNotes/2.4.1.txt[2.4.1],
71 link:RelNotes/2.4.0.txt[2.4].
73 * link:v2.3.9/git.html[documentation for release 2.3.9]
76 link:RelNotes/2.3.9.txt[2.3.9],
77 link:RelNotes/2.3.8.txt[2.3.8],
78 link:RelNotes/2.3.7.txt[2.3.7],
79 link:RelNotes/2.3.6.txt[2.3.6],
80 link:RelNotes/2.3.5.txt[2.3.5],
81 link:RelNotes/2.3.4.txt[2.3.4],
82 link:RelNotes/2.3.3.txt[2.3.3],
83 link:RelNotes/2.3.2.txt[2.3.2],
84 link:RelNotes/2.3.1.txt[2.3.1],
85 link:RelNotes/2.3.0.txt[2.3].
87 * link:v2.2.3/git.html[documentation for release 2.2.3]
90 link:RelNotes/2.2.3.txt[2.2.3],
91 link:RelNotes/2.2.2.txt[2.2.2],
92 link:RelNotes/2.2.1.txt[2.2.1],
93 link:RelNotes/2.2.0.txt[2.2].
95 * link:v2.1.4/git.html[documentation for release 2.1.4]
98 link:RelNotes/2.1.4.txt[2.1.4],
99 link:RelNotes/2.1.3.txt[2.1.3],
100 link:RelNotes/2.1.2.txt[2.1.2],
101 link:RelNotes/2.1.1.txt[2.1.1],
102 link:RelNotes/2.1.0.txt[2.1].
104 * link:v2.0.5/git.html[documentation for release 2.0.5]
107 link:RelNotes/2.0.5.txt[2.0.5],
108 link:RelNotes/2.0.4.txt[2.0.4],
109 link:RelNotes/2.0.3.txt[2.0.3],
110 link:RelNotes/2.0.2.txt[2.0.2],
111 link:RelNotes/2.0.1.txt[2.0.1],
112 link:RelNotes/2.0.0.txt[2.0.0].
114 * link:v1.9.5/git.html[documentation for release 1.9.5]
117 link:RelNotes/1.9.5.txt[1.9.5],
118 link:RelNotes/1.9.4.txt[1.9.4],
119 link:RelNotes/1.9.3.txt[1.9.3],
120 link:RelNotes/1.9.2.txt[1.9.2],
121 link:RelNotes/1.9.1.txt[1.9.1],
122 link:RelNotes/1.9.0.txt[1.9.0].
124 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
127 link:RelNotes/1.8.5.6.txt[1.8.5.6],
128 link:RelNotes/1.8.5.5.txt[1.8.5.5],
129 link:RelNotes/1.8.5.4.txt[1.8.5.4],
130 link:RelNotes/1.8.5.3.txt[1.8.5.3],
131 link:RelNotes/1.8.5.2.txt[1.8.5.2],
132 link:RelNotes/1.8.5.1.txt[1.8.5.1],
133 link:RelNotes/1.8.5.txt[1.8.5].
135 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
138 link:RelNotes/1.8.4.5.txt[1.8.4.5],
139 link:RelNotes/1.8.4.4.txt[1.8.4.4],
140 link:RelNotes/1.8.4.3.txt[1.8.4.3],
141 link:RelNotes/1.8.4.2.txt[1.8.4.2],
142 link:RelNotes/1.8.4.1.txt[1.8.4.1],
143 link:RelNotes/1.8.4.txt[1.8.4].
145 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
148 link:RelNotes/1.8.3.4.txt[1.8.3.4],
149 link:RelNotes/1.8.3.3.txt[1.8.3.3],
150 link:RelNotes/1.8.3.2.txt[1.8.3.2],
151 link:RelNotes/1.8.3.1.txt[1.8.3.1],
152 link:RelNotes/1.8.3.txt[1.8.3].
154 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
157 link:RelNotes/1.8.2.3.txt[1.8.2.3],
158 link:RelNotes/1.8.2.2.txt[1.8.2.2],
159 link:RelNotes/1.8.2.1.txt[1.8.2.1],
160 link:RelNotes/1.8.2.txt[1.8.2].
162 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
165 link:RelNotes/1.8.1.6.txt[1.8.1.6],
166 link:RelNotes/1.8.1.5.txt[1.8.1.5],
167 link:RelNotes/1.8.1.4.txt[1.8.1.4],
168 link:RelNotes/1.8.1.3.txt[1.8.1.3],
169 link:RelNotes/1.8.1.2.txt[1.8.1.2],
170 link:RelNotes/1.8.1.1.txt[1.8.1.1],
171 link:RelNotes/1.8.1.txt[1.8.1].
173 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
176 link:RelNotes/1.8.0.3.txt[1.8.0.3],
177 link:RelNotes/1.8.0.2.txt[1.8.0.2],
178 link:RelNotes/1.8.0.1.txt[1.8.0.1],
179 link:RelNotes/1.8.0.txt[1.8.0].
181 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
184 link:RelNotes/1.7.12.4.txt[1.7.12.4],
185 link:RelNotes/1.7.12.3.txt[1.7.12.3],
186 link:RelNotes/1.7.12.2.txt[1.7.12.2],
187 link:RelNotes/1.7.12.1.txt[1.7.12.1],
188 link:RelNotes/1.7.12.txt[1.7.12].
190 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
193 link:RelNotes/1.7.11.7.txt[1.7.11.7],
194 link:RelNotes/1.7.11.6.txt[1.7.11.6],
195 link:RelNotes/1.7.11.5.txt[1.7.11.5],
196 link:RelNotes/1.7.11.4.txt[1.7.11.4],
197 link:RelNotes/1.7.11.3.txt[1.7.11.3],
198 link:RelNotes/1.7.11.2.txt[1.7.11.2],
199 link:RelNotes/1.7.11.1.txt[1.7.11.1],
200 link:RelNotes/1.7.11.txt[1.7.11].
202 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
205 link:RelNotes/1.7.10.5.txt[1.7.10.5],
206 link:RelNotes/1.7.10.4.txt[1.7.10.4],
207 link:RelNotes/1.7.10.3.txt[1.7.10.3],
208 link:RelNotes/1.7.10.2.txt[1.7.10.2],
209 link:RelNotes/1.7.10.1.txt[1.7.10.1],
210 link:RelNotes/1.7.10.txt[1.7.10].
212 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
215 link:RelNotes/1.7.9.7.txt[1.7.9.7],
216 link:RelNotes/1.7.9.6.txt[1.7.9.6],
217 link:RelNotes/1.7.9.5.txt[1.7.9.5],
218 link:RelNotes/1.7.9.4.txt[1.7.9.4],
219 link:RelNotes/1.7.9.3.txt[1.7.9.3],
220 link:RelNotes/1.7.9.2.txt[1.7.9.2],
221 link:RelNotes/1.7.9.1.txt[1.7.9.1],
222 link:RelNotes/1.7.9.txt[1.7.9].
224 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
227 link:RelNotes/1.7.8.6.txt[1.7.8.6],
228 link:RelNotes/1.7.8.5.txt[1.7.8.5],
229 link:RelNotes/1.7.8.4.txt[1.7.8.4],
230 link:RelNotes/1.7.8.3.txt[1.7.8.3],
231 link:RelNotes/1.7.8.2.txt[1.7.8.2],
232 link:RelNotes/1.7.8.1.txt[1.7.8.1],
233 link:RelNotes/1.7.8.txt[1.7.8].
235 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
238 link:RelNotes/1.7.7.7.txt[1.7.7.7],
239 link:RelNotes/1.7.7.6.txt[1.7.7.6],
240 link:RelNotes/1.7.7.5.txt[1.7.7.5],
241 link:RelNotes/1.7.7.4.txt[1.7.7.4],
242 link:RelNotes/1.7.7.3.txt[1.7.7.3],
243 link:RelNotes/1.7.7.2.txt[1.7.7.2],
244 link:RelNotes/1.7.7.1.txt[1.7.7.1],
245 link:RelNotes/1.7.7.txt[1.7.7].
247 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
250 link:RelNotes/1.7.6.6.txt[1.7.6.6],
251 link:RelNotes/1.7.6.5.txt[1.7.6.5],
252 link:RelNotes/1.7.6.4.txt[1.7.6.4],
253 link:RelNotes/1.7.6.3.txt[1.7.6.3],
254 link:RelNotes/1.7.6.2.txt[1.7.6.2],
255 link:RelNotes/1.7.6.1.txt[1.7.6.1],
256 link:RelNotes/1.7.6.txt[1.7.6].
258 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
261 link:RelNotes/1.7.5.4.txt[1.7.5.4],
262 link:RelNotes/1.7.5.3.txt[1.7.5.3],
263 link:RelNotes/1.7.5.2.txt[1.7.5.2],
264 link:RelNotes/1.7.5.1.txt[1.7.5.1],
265 link:RelNotes/1.7.5.txt[1.7.5].
267 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
270 link:RelNotes/1.7.4.5.txt[1.7.4.5],
271 link:RelNotes/1.7.4.4.txt[1.7.4.4],
272 link:RelNotes/1.7.4.3.txt[1.7.4.3],
273 link:RelNotes/1.7.4.2.txt[1.7.4.2],
274 link:RelNotes/1.7.4.1.txt[1.7.4.1],
275 link:RelNotes/1.7.4.txt[1.7.4].
277 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
280 link:RelNotes/1.7.3.5.txt[1.7.3.5],
281 link:RelNotes/1.7.3.4.txt[1.7.3.4],
282 link:RelNotes/1.7.3.3.txt[1.7.3.3],
283 link:RelNotes/1.7.3.2.txt[1.7.3.2],
284 link:RelNotes/1.7.3.1.txt[1.7.3.1],
285 link:RelNotes/1.7.3.txt[1.7.3].
287 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
290 link:RelNotes/1.7.2.5.txt[1.7.2.5],
291 link:RelNotes/1.7.2.4.txt[1.7.2.4],
292 link:RelNotes/1.7.2.3.txt[1.7.2.3],
293 link:RelNotes/1.7.2.2.txt[1.7.2.2],
294 link:RelNotes/1.7.2.1.txt[1.7.2.1],
295 link:RelNotes/1.7.2.txt[1.7.2].
297 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
300 link:RelNotes/1.7.1.4.txt[1.7.1.4],
301 link:RelNotes/1.7.1.3.txt[1.7.1.3],
302 link:RelNotes/1.7.1.2.txt[1.7.1.2],
303 link:RelNotes/1.7.1.1.txt[1.7.1.1],
304 link:RelNotes/1.7.1.txt[1.7.1].
306 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
309 link:RelNotes/1.7.0.9.txt[1.7.0.9],
310 link:RelNotes/1.7.0.8.txt[1.7.0.8],
311 link:RelNotes/1.7.0.7.txt[1.7.0.7],
312 link:RelNotes/1.7.0.6.txt[1.7.0.6],
313 link:RelNotes/1.7.0.5.txt[1.7.0.5],
314 link:RelNotes/1.7.0.4.txt[1.7.0.4],
315 link:RelNotes/1.7.0.3.txt[1.7.0.3],
316 link:RelNotes/1.7.0.2.txt[1.7.0.2],
317 link:RelNotes/1.7.0.1.txt[1.7.0.1],
318 link:RelNotes/1.7.0.txt[1.7.0].
320 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
323 link:RelNotes/1.6.6.3.txt[1.6.6.3],
324 link:RelNotes/1.6.6.2.txt[1.6.6.2],
325 link:RelNotes/1.6.6.1.txt[1.6.6.1],
326 link:RelNotes/1.6.6.txt[1.6.6].
328 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
331 link:RelNotes/1.6.5.9.txt[1.6.5.9],
332 link:RelNotes/1.6.5.8.txt[1.6.5.8],
333 link:RelNotes/1.6.5.7.txt[1.6.5.7],
334 link:RelNotes/1.6.5.6.txt[1.6.5.6],
335 link:RelNotes/1.6.5.5.txt[1.6.5.5],
336 link:RelNotes/1.6.5.4.txt[1.6.5.4],
337 link:RelNotes/1.6.5.3.txt[1.6.5.3],
338 link:RelNotes/1.6.5.2.txt[1.6.5.2],
339 link:RelNotes/1.6.5.1.txt[1.6.5.1],
340 link:RelNotes/1.6.5.txt[1.6.5].
342 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
345 link:RelNotes/1.6.4.5.txt[1.6.4.5],
346 link:RelNotes/1.6.4.4.txt[1.6.4.4],
347 link:RelNotes/1.6.4.3.txt[1.6.4.3],
348 link:RelNotes/1.6.4.2.txt[1.6.4.2],
349 link:RelNotes/1.6.4.1.txt[1.6.4.1],
350 link:RelNotes/1.6.4.txt[1.6.4].
352 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
355 link:RelNotes/1.6.3.4.txt[1.6.3.4],
356 link:RelNotes/1.6.3.3.txt[1.6.3.3],
357 link:RelNotes/1.6.3.2.txt[1.6.3.2],
358 link:RelNotes/1.6.3.1.txt[1.6.3.1],
359 link:RelNotes/1.6.3.txt[1.6.3].
362 link:RelNotes/1.6.2.5.txt[1.6.2.5],
363 link:RelNotes/1.6.2.4.txt[1.6.2.4],
364 link:RelNotes/1.6.2.3.txt[1.6.2.3],
365 link:RelNotes/1.6.2.2.txt[1.6.2.2],
366 link:RelNotes/1.6.2.1.txt[1.6.2.1],
367 link:RelNotes/1.6.2.txt[1.6.2].
369 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
372 link:RelNotes/1.6.1.3.txt[1.6.1.3],
373 link:RelNotes/1.6.1.2.txt[1.6.1.2],
374 link:RelNotes/1.6.1.1.txt[1.6.1.1],
375 link:RelNotes/1.6.1.txt[1.6.1].
377 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
380 link:RelNotes/1.6.0.6.txt[1.6.0.6],
381 link:RelNotes/1.6.0.5.txt[1.6.0.5],
382 link:RelNotes/1.6.0.4.txt[1.6.0.4],
383 link:RelNotes/1.6.0.3.txt[1.6.0.3],
384 link:RelNotes/1.6.0.2.txt[1.6.0.2],
385 link:RelNotes/1.6.0.1.txt[1.6.0.1],
386 link:RelNotes/1.6.0.txt[1.6.0].
388 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
391 link:RelNotes/1.5.6.6.txt[1.5.6.6],
392 link:RelNotes/1.5.6.5.txt[1.5.6.5],
393 link:RelNotes/1.5.6.4.txt[1.5.6.4],
394 link:RelNotes/1.5.6.3.txt[1.5.6.3],
395 link:RelNotes/1.5.6.2.txt[1.5.6.2],
396 link:RelNotes/1.5.6.1.txt[1.5.6.1],
397 link:RelNotes/1.5.6.txt[1.5.6].
399 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
402 link:RelNotes/1.5.5.6.txt[1.5.5.6],
403 link:RelNotes/1.5.5.5.txt[1.5.5.5],
404 link:RelNotes/1.5.5.4.txt[1.5.5.4],
405 link:RelNotes/1.5.5.3.txt[1.5.5.3],
406 link:RelNotes/1.5.5.2.txt[1.5.5.2],
407 link:RelNotes/1.5.5.1.txt[1.5.5.1],
408 link:RelNotes/1.5.5.txt[1.5.5].
410 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
413 link:RelNotes/1.5.4.7.txt[1.5.4.7],
414 link:RelNotes/1.5.4.6.txt[1.5.4.6],
415 link:RelNotes/1.5.4.5.txt[1.5.4.5],
416 link:RelNotes/1.5.4.4.txt[1.5.4.4],
417 link:RelNotes/1.5.4.3.txt[1.5.4.3],
418 link:RelNotes/1.5.4.2.txt[1.5.4.2],
419 link:RelNotes/1.5.4.1.txt[1.5.4.1],
420 link:RelNotes/1.5.4.txt[1.5.4].
422 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
425 link:RelNotes/1.5.3.8.txt[1.5.3.8],
426 link:RelNotes/1.5.3.7.txt[1.5.3.7],
427 link:RelNotes/1.5.3.6.txt[1.5.3.6],
428 link:RelNotes/1.5.3.5.txt[1.5.3.5],
429 link:RelNotes/1.5.3.4.txt[1.5.3.4],
430 link:RelNotes/1.5.3.3.txt[1.5.3.3],
431 link:RelNotes/1.5.3.2.txt[1.5.3.2],
432 link:RelNotes/1.5.3.1.txt[1.5.3.1],
433 link:RelNotes/1.5.3.txt[1.5.3].
435 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
438 link:RelNotes/1.5.2.5.txt[1.5.2.5],
439 link:RelNotes/1.5.2.4.txt[1.5.2.4],
440 link:RelNotes/1.5.2.3.txt[1.5.2.3],
441 link:RelNotes/1.5.2.2.txt[1.5.2.2],
442 link:RelNotes/1.5.2.1.txt[1.5.2.1],
443 link:RelNotes/1.5.2.txt[1.5.2].
445 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
448 link:RelNotes/1.5.1.6.txt[1.5.1.6],
449 link:RelNotes/1.5.1.5.txt[1.5.1.5],
450 link:RelNotes/1.5.1.4.txt[1.5.1.4],
451 link:RelNotes/1.5.1.3.txt[1.5.1.3],
452 link:RelNotes/1.5.1.2.txt[1.5.1.2],
453 link:RelNotes/1.5.1.1.txt[1.5.1.1],
454 link:RelNotes/1.5.1.txt[1.5.1].
456 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
459 link:RelNotes/1.5.0.7.txt[1.5.0.7],
460 link:RelNotes/1.5.0.6.txt[1.5.0.6],
461 link:RelNotes/1.5.0.5.txt[1.5.0.5],
462 link:RelNotes/1.5.0.3.txt[1.5.0.3],
463 link:RelNotes/1.5.0.2.txt[1.5.0.2],
464 link:RelNotes/1.5.0.1.txt[1.5.0.1],
465 link:RelNotes/1.5.0.txt[1.5.0].
467 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
468 link:v1.3.3/git.html[1.3.3],
469 link:v1.2.6/git.html[1.2.6],
470 link:v1.0.13/git.html[1.0.13].
479 Prints the Git suite version that the 'git' program came from.
482 Prints the synopsis and a list of the most commonly used
483 commands. If the option '--all' or '-a' is given then all
484 available commands are printed. If a Git command is named this
485 option will bring up the manual page for that command.
487 Other options are available to control how the manual page is
488 displayed. See linkgit:git-help[1] for more information,
489 because `git --help ...` is converted internally into `git
493 Run as if git was started in '<path>' instead of the current working
494 directory. When multiple `-C` options are given, each subsequent
495 non-absolute `-C <path>` is interpreted relative to the preceding `-C
498 This option affects options that expect path name like `--git-dir` and
499 `--work-tree` in that their interpretations of the path names would be
500 made relative to the working directory caused by the `-C` option. For
501 example the following invocations are equivalent:
503 git --git-dir=a.git --work-tree=b -C c status
504 git --git-dir=c/a.git --work-tree=c/b status
507 Pass a configuration parameter to the command. The value
508 given will override values from configuration files.
509 The <name> is expected in the same format as listed by
510 'git config' (subkeys separated by dots).
512 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
513 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
514 config file). Including the equals but with an empty value (like `git -c
515 foo.bar= ...`) sets `foo.bar` to the empty string.
517 --exec-path[=<path>]::
518 Path to wherever your core Git programs are installed.
519 This can also be controlled by setting the GIT_EXEC_PATH
520 environment variable. If no path is given, 'git' will print
521 the current setting and then exit.
524 Print the path, without trailing slash, where Git's HTML
525 documentation is installed and exit.
528 Print the manpath (see `man(1)`) for the man pages for
529 this version of Git and exit.
532 Print the path where the Info files documenting this
533 version of Git are installed and exit.
537 Pipe all output into 'less' (or if set, $PAGER) if standard
538 output is a terminal. This overrides the `pager.<cmd>`
539 configuration options (see the "Configuration Mechanism" section
543 Do not pipe Git output into a pager.
546 Set the path to the repository. This can also be controlled by
547 setting the GIT_DIR environment variable. It can be an absolute
548 path or relative path to current working directory.
551 Set the path to the working tree. It can be an absolute path
552 or a path relative to the current working directory.
553 This can also be controlled by setting the GIT_WORK_TREE
554 environment variable and the core.worktree configuration
555 variable (see core.worktree in linkgit:git-config[1] for a
556 more detailed discussion).
559 Set the Git namespace. See linkgit:gitnamespaces[7] for more
560 details. Equivalent to setting the `GIT_NAMESPACE` environment
564 Treat the repository as a bare repository. If GIT_DIR
565 environment is not set, it is set to the current working
568 --no-replace-objects::
569 Do not use replacement refs to replace Git objects. See
570 linkgit:git-replace[1] for more information.
572 --literal-pathspecs::
573 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
574 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
578 Add "glob" magic to all pathspec. This is equivalent to setting
579 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
580 globbing on individual pathspecs can be done using pathspec
584 Add "literal" magic to all pathspec. This is equivalent to setting
585 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
586 globbing on individual pathspecs can be done using pathspec
590 Add "icase" magic to all pathspec. This is equivalent to setting
591 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
596 We divide Git into high level ("porcelain") commands and low level
597 ("plumbing") commands.
599 High-level commands (porcelain)
600 -------------------------------
602 We separate the porcelain commands into the main commands and some
603 ancillary user utilities.
605 Main porcelain commands
606 ~~~~~~~~~~~~~~~~~~~~~~~
608 include::cmds-mainporcelain.txt[]
614 include::cmds-ancillarymanipulators.txt[]
618 include::cmds-ancillaryinterrogators.txt[]
621 Interacting with Others
622 ~~~~~~~~~~~~~~~~~~~~~~~
624 These commands are to interact with foreign SCM and with other
625 people via patch over e-mail.
627 include::cmds-foreignscminterface.txt[]
630 Low-level commands (plumbing)
631 -----------------------------
633 Although Git includes its
634 own porcelain layer, its low-level commands are sufficient to support
635 development of alternative porcelains. Developers of such porcelains
636 might start by reading about linkgit:git-update-index[1] and
637 linkgit:git-read-tree[1].
639 The interface (input, output, set of options and the semantics)
640 to these low-level commands are meant to be a lot more stable
641 than Porcelain level commands, because these commands are
642 primarily for scripted use. The interface to Porcelain commands
643 on the other hand are subject to change in order to improve the
646 The following description divides
647 the low-level commands into commands that manipulate objects (in
648 the repository, index, and working tree), commands that interrogate and
649 compare objects, and commands that move objects and references between
653 Manipulation commands
654 ~~~~~~~~~~~~~~~~~~~~~
656 include::cmds-plumbingmanipulators.txt[]
659 Interrogation commands
660 ~~~~~~~~~~~~~~~~~~~~~~
662 include::cmds-plumbinginterrogators.txt[]
664 In general, the interrogate commands do not touch the files in
668 Synching repositories
669 ~~~~~~~~~~~~~~~~~~~~~
671 include::cmds-synchingrepositories.txt[]
673 The following are helper commands used by the above; end users
674 typically do not use them directly.
676 include::cmds-synchelpers.txt[]
679 Internal helper commands
680 ~~~~~~~~~~~~~~~~~~~~~~~~
682 These are internal helper commands used by other commands; end
683 users typically do not use them directly.
685 include::cmds-purehelpers.txt[]
688 Configuration Mechanism
689 -----------------------
691 Git uses a simple text format to store customizations that are per
692 repository and are per user. Such a configuration file may look
697 # A '#' or ';' character indicates a comment.
702 ; Don't trust file modes
707 name = "Junio C Hamano"
708 email = "gitster@pobox.com"
712 Various commands read from the configuration file and adjust
713 their operation accordingly. See linkgit:git-config[1] for a
714 list and more details about the configuration mechanism.
717 Identifier Terminology
718 ----------------------
720 Indicates the object name for any type of object.
723 Indicates a blob object name.
726 Indicates a tree object name.
729 Indicates a commit object name.
732 Indicates a tree, commit or tag object name. A
733 command that takes a <tree-ish> argument ultimately wants to
734 operate on a <tree> object but automatically dereferences
735 <commit> and <tag> objects that point at a <tree>.
738 Indicates a commit or tag object name. A
739 command that takes a <commit-ish> argument ultimately wants to
740 operate on a <commit> object but automatically dereferences
741 <tag> objects that point at a <commit>.
744 Indicates that an object type is required.
745 Currently one of: `blob`, `tree`, `commit`, or `tag`.
748 Indicates a filename - almost always relative to the
749 root of the tree structure `GIT_INDEX_FILE` describes.
753 Any Git command accepting any <object> can also use the following
757 indicates the head of the current branch.
761 (i.e. a `refs/tags/<tag>` reference).
765 (i.e. a `refs/heads/<head>` reference).
767 For a more complete list of ways to spell object names, see
768 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
771 File/Directory Structure
772 ------------------------
774 Please see the linkgit:gitrepository-layout[5] document.
776 Read linkgit:githooks[5] for more details about each hook.
778 Higher level SCMs may provide and manage additional information in the
784 Please see linkgit:gitglossary[7].
787 Environment Variables
788 ---------------------
789 Various Git commands use the following environment variables:
793 These environment variables apply to 'all' core Git commands. Nb: it
794 is worth noting that they may be used/overridden by SCMS sitting above
795 Git so take care if using a foreign front-end.
798 This environment allows the specification of an alternate
799 index file. If not specified, the default of `$GIT_DIR/index`
802 'GIT_INDEX_VERSION'::
803 This environment variable allows the specification of an index
804 version for new repositories. It won't affect existing index
805 files. By default index file version 2 or 3 is used. See
806 linkgit:git-update-index[1] for more information.
808 'GIT_OBJECT_DIRECTORY'::
809 If the object storage directory is specified via this
810 environment variable then the sha1 directories are created
811 underneath - otherwise the default `$GIT_DIR/objects`
814 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
815 Due to the immutable nature of Git objects, old objects can be
816 archived into shared, read-only directories. This variable
817 specifies a ":" separated (on Windows ";" separated) list
818 of Git object directories which can be used to search for Git
819 objects. New objects will not be written to these directories.
822 If the 'GIT_DIR' environment variable is set then it
823 specifies a path to use instead of the default `.git`
824 for the base of the repository.
825 The '--git-dir' command-line option also sets this value.
828 Set the path to the root of the working tree.
829 This can also be controlled by the '--work-tree' command-line
830 option and the core.worktree configuration variable.
833 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
834 The '--namespace' command-line option also sets this value.
836 'GIT_CEILING_DIRECTORIES'::
837 This should be a colon-separated list of absolute paths. If
838 set, it is a list of directories that Git should not chdir up
839 into while looking for a repository directory (useful for
840 excluding slow-loading network directories). It will not
841 exclude the current working directory or a GIT_DIR set on the
842 command line or in the environment. Normally, Git has to read
843 the entries in this list and resolve any symlink that
844 might be present in order to compare them with the current
845 directory. However, if even this access is slow, you
846 can add an empty entry to the list to tell Git that the
847 subsequent entries are not symlinks and needn't be resolved;
849 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
851 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
852 When run in a directory that does not have ".git" repository
853 directory, Git tries to find such a directory in the parent
854 directories to find the top of the working tree, but by default it
855 does not cross filesystem boundaries. This environment variable
856 can be set to true to tell Git not to stop at filesystem
857 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
858 an explicit repository directory set via 'GIT_DIR' or on the
862 If this variable is set to a path, non-worktree files that are
863 normally in $GIT_DIR will be taken from this path
864 instead. Worktree-specific files such as HEAD or index are
865 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
866 linkgit:git-worktree[1] for
867 details. This variable has lower precedence than other path
868 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
875 'GIT_COMMITTER_NAME'::
876 'GIT_COMMITTER_EMAIL'::
877 'GIT_COMMITTER_DATE'::
879 see linkgit:git-commit-tree[1]
884 Only valid setting is "--unified=??" or "-u??" to set the
885 number of context lines shown when a unified diff is created.
886 This takes precedence over any "-U" or "--unified" option
887 value passed on the Git diff command line.
889 'GIT_EXTERNAL_DIFF'::
890 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
891 program named by it is called, instead of the diff invocation
892 described above. For a path that is added, removed, or modified,
893 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
895 path old-file old-hex old-mode new-file new-hex new-mode
899 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
900 contents of <old|new>,
901 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
902 <old|new>-mode:: are the octal representation of the file modes.
904 The file parameters can point at the user's working file
905 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
906 when a new file is added), or a temporary file (e.g. `old-file` in the
907 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
908 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
910 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
913 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
914 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
916 'GIT_DIFF_PATH_COUNTER'::
917 A 1-based counter incremented by one for every path.
919 'GIT_DIFF_PATH_TOTAL'::
920 The total number of paths.
924 'GIT_MERGE_VERBOSITY'::
925 A number controlling the amount of output shown by
926 the recursive merge strategy. Overrides merge.verbosity.
927 See linkgit:git-merge[1]
930 This environment variable overrides `$PAGER`. If it is set
931 to an empty string or to the value "cat", Git will not launch
932 a pager. See also the `core.pager` option in
933 linkgit:git-config[1].
936 This environment variable overrides `$EDITOR` and `$VISUAL`.
937 It is used by several Git commands when, on interactive mode,
938 an editor is to be launched. See also linkgit:git-var[1]
939 and the `core.editor` option in linkgit:git-config[1].
943 If either of these environment variables is set then 'git fetch'
944 and 'git push' will use the specified command instead of 'ssh'
945 when they need to connect to a remote system.
946 The command will be given exactly two or four arguments: the
947 'username@host' (or just 'host') from the URL and the shell
948 command to execute on that remote system, optionally preceded by
949 '-p' (literally) and the 'port' from the URL when it specifies
950 something other than the default SSH port.
952 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
953 by the shell, which allows additional arguments to be included.
954 `$GIT_SSH` on the other hand must be just the path to a program
955 (which can be a wrapper shell script, if additional arguments are
958 Usually it is easier to configure any desired options through your
959 personal `.ssh/config` file. Please consult your ssh documentation
963 If this environment variable is set, then Git commands which need to
964 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
965 will call this program with a suitable prompt as command-line argument
966 and read the password from its STDOUT. See also the 'core.askPass'
967 option in linkgit:git-config[1].
969 'GIT_TERMINAL_PROMPT'::
970 If this environment variable is set to `0`, git will not prompt
971 on the terminal (e.g., when asking for HTTP authentication).
973 'GIT_CONFIG_NOSYSTEM'::
974 Whether to skip reading settings from the system-wide
975 `$(prefix)/etc/gitconfig` file. This environment variable can
976 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
977 predictable environment for a picky script, or you can set it
978 temporarily to avoid using a buggy `/etc/gitconfig` file while
979 waiting for someone with sufficient permissions to fix it.
982 If this environment variable is set to "1", then commands such
983 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
984 'git check-attr' and 'git check-ignore' will
985 force a flush of the output stream after each record have been
987 variable is set to "0", the output of these commands will be done
988 using completely buffered I/O. If this environment variable is
989 not set, Git will choose buffered or record-oriented flushing
990 based on whether stdout appears to be redirected to a file or not.
993 Enables general trace messages, e.g. alias expansion, built-in
994 command execution and external command execution.
996 If this variable is set to "1", "2" or "true" (comparison
997 is case insensitive), trace messages will be printed to
1000 If the variable is set to an integer value greater than 2
1001 and lower than 10 (strictly) then Git will interpret this
1002 value as an open file descriptor and will try to write the
1003 trace messages into this file descriptor.
1005 Alternatively, if the variable is set to an absolute path
1006 (starting with a '/' character), Git will interpret this
1007 as a file path and will try to write the trace messages
1010 Unsetting the variable, or setting it to empty, "0" or
1011 "false" (case insensitive) disables trace messages.
1013 'GIT_TRACE_PACK_ACCESS'::
1014 Enables trace messages for all accesses to any packs. For each
1015 access, the pack file name and an offset in the pack is
1016 recorded. This may be helpful for troubleshooting some
1017 pack-related performance problems.
1018 See 'GIT_TRACE' for available trace output options.
1020 'GIT_TRACE_PACKET'::
1021 Enables trace messages for all packets coming in or out of a
1022 given program. This can help with debugging object negotiation
1023 or other protocol issues. Tracing is turned off at a packet
1024 starting with "PACK" (but see 'GIT_TRACE_PACKFILE' below).
1025 See 'GIT_TRACE' for available trace output options.
1027 'GIT_TRACE_PACKFILE'::
1028 Enables tracing of packfiles sent or received by a
1029 given program. Unlike other trace output, this trace is
1030 verbatim: no headers, and no quoting of binary data. You almost
1031 certainly want to direct into a file (e.g.,
1032 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1033 the terminal or mixing it with other trace output.
1035 Note that this is currently only implemented for the client side
1036 of clones and fetches.
1038 'GIT_TRACE_PERFORMANCE'::
1039 Enables performance related trace messages, e.g. total execution
1040 time of each Git command.
1041 See 'GIT_TRACE' for available trace output options.
1044 Enables trace messages printing the .git, working tree and current
1045 working directory after Git has completed its setup phase.
1046 See 'GIT_TRACE' for available trace output options.
1048 'GIT_TRACE_SHALLOW'::
1049 Enables trace messages that can help debugging fetching /
1050 cloning of shallow repositories.
1051 See 'GIT_TRACE' for available trace output options.
1053 GIT_LITERAL_PATHSPECS::
1054 Setting this variable to `1` will cause Git to treat all
1055 pathspecs literally, rather than as glob patterns. For example,
1056 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1057 for commits that touch the path `*.c`, not any paths that the
1058 glob `*.c` matches. You might want this if you are feeding
1059 literal paths to Git (e.g., paths previously given to you by
1060 `git ls-tree`, `--raw` diff output, etc).
1062 GIT_GLOB_PATHSPECS::
1063 Setting this variable to `1` will cause Git to treat all
1064 pathspecs as glob patterns (aka "glob" magic).
1066 GIT_NOGLOB_PATHSPECS::
1067 Setting this variable to `1` will cause Git to treat all
1068 pathspecs as literal (aka "literal" magic).
1070 GIT_ICASE_PATHSPECS::
1071 Setting this variable to `1` will cause Git to treat all
1072 pathspecs as case-insensitive.
1074 'GIT_REFLOG_ACTION'::
1075 When a ref is updated, reflog entries are created to keep
1076 track of the reason why the ref was updated (which is
1077 typically the name of the high-level command that updated
1078 the ref), in addition to the old and new values of the ref.
1079 A scripted Porcelain command can use set_reflog_action
1080 helper function in `git-sh-setup` to set its name to this
1081 variable when it is invoked as the top level command by the
1082 end user, to be recorded in the body of the reflog.
1084 `GIT_REF_PARANOIA`::
1085 If set to `1`, include broken or badly named refs when iterating
1086 over lists of refs. In a normal, non-corrupted repository, this
1087 does nothing. However, enabling it may help git to detect and
1088 abort some operations in the presence of broken refs. Git sets
1089 this variable automatically when performing destructive
1090 operations like linkgit:git-prune[1]. You should not need to set
1091 it yourself unless you want to be paranoid about making sure
1092 an operation has touched every ref (e.g., because you are
1093 cloning a repository to make a backup).
1096 Discussion[[Discussion]]
1097 ------------------------
1099 More detail on the following is available from the
1100 link:user-manual.html#git-concepts[Git concepts chapter of the
1101 user-manual] and linkgit:gitcore-tutorial[7].
1103 A Git project normally consists of a working directory with a ".git"
1104 subdirectory at the top level. The .git directory contains, among other
1105 things, a compressed object database representing the complete history
1106 of the project, an "index" file which links that history to the current
1107 contents of the working tree, and named pointers into that history such
1108 as tags and branch heads.
1110 The object database contains objects of three main types: blobs, which
1111 hold file data; trees, which point to blobs and other trees to build up
1112 directory hierarchies; and commits, which each reference a single tree
1113 and some number of parent commits.
1115 The commit, equivalent to what other systems call a "changeset" or
1116 "version", represents a step in the project's history, and each parent
1117 represents an immediately preceding step. Commits with more than one
1118 parent represent merges of independent lines of development.
1120 All objects are named by the SHA-1 hash of their contents, normally
1121 written as a string of 40 hex digits. Such names are globally unique.
1122 The entire history leading up to a commit can be vouched for by signing
1123 just that commit. A fourth object type, the tag, is provided for this
1126 When first created, objects are stored in individual files, but for
1127 efficiency may later be compressed together into "pack files".
1129 Named pointers called refs mark interesting points in history. A ref
1130 may contain the SHA-1 name of an object or the name of another ref. Refs
1131 with names beginning `ref/head/` contain the SHA-1 name of the most
1132 recent commit (or "head") of a branch under development. SHA-1 names of
1133 tags of interest are stored under `ref/tags/`. A special ref named
1134 `HEAD` contains the name of the currently checked-out branch.
1136 The index file is initialized with a list of all paths and, for each
1137 path, a blob object and a set of attributes. The blob object represents
1138 the contents of the file as of the head of the current branch. The
1139 attributes (last modified time, size, etc.) are taken from the
1140 corresponding file in the working tree. Subsequent changes to the
1141 working tree can be found by comparing these attributes. The index may
1142 be updated with new content, and new commits may be created from the
1143 content stored in the index.
1145 The index is also capable of storing multiple entries (called "stages")
1146 for a given pathname. These stages are used to hold the various
1147 unmerged version of a file when a merge is in progress.
1149 FURTHER DOCUMENTATION
1150 ---------------------
1152 See the references in the "description" section to get started
1153 using Git. The following is probably more detail than necessary
1154 for a first-time user.
1156 The link:user-manual.html#git-concepts[Git concepts chapter of the
1157 user-manual] and linkgit:gitcore-tutorial[7] both provide
1158 introductions to the underlying Git architecture.
1160 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1162 See also the link:howto-index.html[howto] documents for some useful
1165 The internals are documented in the
1166 link:technical/api-index.html[Git API documentation].
1168 Users migrating from CVS may also want to
1169 read linkgit:gitcvs-migration[7].
1174 Git was started by Linus Torvalds, and is currently maintained by Junio
1175 C Hamano. Numerous contributions have come from the Git mailing list
1176 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1177 gives you a more complete list of contributors.
1179 If you have a clone of git.git itself, the
1180 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1181 the authors for specific parts of the project.
1186 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1187 development and maintenance is primarily done. You do not have to be
1188 subscribed to the list to send a message there.
1192 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1193 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1194 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1195 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1196 linkgit:gitworkflows[7]
1200 Part of the linkgit:git[1] suite