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.1/git.html[documentation for release 2.6.1]
49 link:RelNotes/2.6.1.txt[2.6.1],
50 link:RelNotes/2.6.0.txt[2.6].
52 * link:v2.5.4/git.html[documentation for release 2.5.4]
55 link:RelNotes/2.5.4.txt[2.5.4],
56 link:RelNotes/2.5.3.txt[2.5.3],
57 link:RelNotes/2.5.2.txt[2.5.2],
58 link:RelNotes/2.5.1.txt[2.5.1],
59 link:RelNotes/2.5.0.txt[2.5].
61 * link:v2.4.10/git.html[documentation for release 2.4.10]
64 link:RelNotes/2.4.10.txt[2.4.10],
65 link:RelNotes/2.4.9.txt[2.4.9],
66 link:RelNotes/2.4.8.txt[2.4.8],
67 link:RelNotes/2.4.7.txt[2.4.7],
68 link:RelNotes/2.4.6.txt[2.4.6],
69 link:RelNotes/2.4.5.txt[2.4.5],
70 link:RelNotes/2.4.4.txt[2.4.4],
71 link:RelNotes/2.4.3.txt[2.4.3],
72 link:RelNotes/2.4.2.txt[2.4.2],
73 link:RelNotes/2.4.1.txt[2.4.1],
74 link:RelNotes/2.4.0.txt[2.4].
76 * link:v2.3.10/git.html[documentation for release 2.3.10]
79 link:RelNotes/2.3.10.txt[2.3.10],
80 link:RelNotes/2.3.9.txt[2.3.9],
81 link:RelNotes/2.3.8.txt[2.3.8],
82 link:RelNotes/2.3.7.txt[2.3.7],
83 link:RelNotes/2.3.6.txt[2.3.6],
84 link:RelNotes/2.3.5.txt[2.3.5],
85 link:RelNotes/2.3.4.txt[2.3.4],
86 link:RelNotes/2.3.3.txt[2.3.3],
87 link:RelNotes/2.3.2.txt[2.3.2],
88 link:RelNotes/2.3.1.txt[2.3.1],
89 link:RelNotes/2.3.0.txt[2.3].
91 * link:v2.2.3/git.html[documentation for release 2.2.3]
94 link:RelNotes/2.2.3.txt[2.2.3],
95 link:RelNotes/2.2.2.txt[2.2.2],
96 link:RelNotes/2.2.1.txt[2.2.1],
97 link:RelNotes/2.2.0.txt[2.2].
99 * link:v2.1.4/git.html[documentation for release 2.1.4]
102 link:RelNotes/2.1.4.txt[2.1.4],
103 link:RelNotes/2.1.3.txt[2.1.3],
104 link:RelNotes/2.1.2.txt[2.1.2],
105 link:RelNotes/2.1.1.txt[2.1.1],
106 link:RelNotes/2.1.0.txt[2.1].
108 * link:v2.0.5/git.html[documentation for release 2.0.5]
111 link:RelNotes/2.0.5.txt[2.0.5],
112 link:RelNotes/2.0.4.txt[2.0.4],
113 link:RelNotes/2.0.3.txt[2.0.3],
114 link:RelNotes/2.0.2.txt[2.0.2],
115 link:RelNotes/2.0.1.txt[2.0.1],
116 link:RelNotes/2.0.0.txt[2.0.0].
118 * link:v1.9.5/git.html[documentation for release 1.9.5]
121 link:RelNotes/1.9.5.txt[1.9.5],
122 link:RelNotes/1.9.4.txt[1.9.4],
123 link:RelNotes/1.9.3.txt[1.9.3],
124 link:RelNotes/1.9.2.txt[1.9.2],
125 link:RelNotes/1.9.1.txt[1.9.1],
126 link:RelNotes/1.9.0.txt[1.9.0].
128 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
131 link:RelNotes/1.8.5.6.txt[1.8.5.6],
132 link:RelNotes/1.8.5.5.txt[1.8.5.5],
133 link:RelNotes/1.8.5.4.txt[1.8.5.4],
134 link:RelNotes/1.8.5.3.txt[1.8.5.3],
135 link:RelNotes/1.8.5.2.txt[1.8.5.2],
136 link:RelNotes/1.8.5.1.txt[1.8.5.1],
137 link:RelNotes/1.8.5.txt[1.8.5].
139 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
142 link:RelNotes/1.8.4.5.txt[1.8.4.5],
143 link:RelNotes/1.8.4.4.txt[1.8.4.4],
144 link:RelNotes/1.8.4.3.txt[1.8.4.3],
145 link:RelNotes/1.8.4.2.txt[1.8.4.2],
146 link:RelNotes/1.8.4.1.txt[1.8.4.1],
147 link:RelNotes/1.8.4.txt[1.8.4].
149 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
152 link:RelNotes/1.8.3.4.txt[1.8.3.4],
153 link:RelNotes/1.8.3.3.txt[1.8.3.3],
154 link:RelNotes/1.8.3.2.txt[1.8.3.2],
155 link:RelNotes/1.8.3.1.txt[1.8.3.1],
156 link:RelNotes/1.8.3.txt[1.8.3].
158 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
161 link:RelNotes/1.8.2.3.txt[1.8.2.3],
162 link:RelNotes/1.8.2.2.txt[1.8.2.2],
163 link:RelNotes/1.8.2.1.txt[1.8.2.1],
164 link:RelNotes/1.8.2.txt[1.8.2].
166 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
169 link:RelNotes/1.8.1.6.txt[1.8.1.6],
170 link:RelNotes/1.8.1.5.txt[1.8.1.5],
171 link:RelNotes/1.8.1.4.txt[1.8.1.4],
172 link:RelNotes/1.8.1.3.txt[1.8.1.3],
173 link:RelNotes/1.8.1.2.txt[1.8.1.2],
174 link:RelNotes/1.8.1.1.txt[1.8.1.1],
175 link:RelNotes/1.8.1.txt[1.8.1].
177 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
180 link:RelNotes/1.8.0.3.txt[1.8.0.3],
181 link:RelNotes/1.8.0.2.txt[1.8.0.2],
182 link:RelNotes/1.8.0.1.txt[1.8.0.1],
183 link:RelNotes/1.8.0.txt[1.8.0].
185 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
188 link:RelNotes/1.7.12.4.txt[1.7.12.4],
189 link:RelNotes/1.7.12.3.txt[1.7.12.3],
190 link:RelNotes/1.7.12.2.txt[1.7.12.2],
191 link:RelNotes/1.7.12.1.txt[1.7.12.1],
192 link:RelNotes/1.7.12.txt[1.7.12].
194 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
197 link:RelNotes/1.7.11.7.txt[1.7.11.7],
198 link:RelNotes/1.7.11.6.txt[1.7.11.6],
199 link:RelNotes/1.7.11.5.txt[1.7.11.5],
200 link:RelNotes/1.7.11.4.txt[1.7.11.4],
201 link:RelNotes/1.7.11.3.txt[1.7.11.3],
202 link:RelNotes/1.7.11.2.txt[1.7.11.2],
203 link:RelNotes/1.7.11.1.txt[1.7.11.1],
204 link:RelNotes/1.7.11.txt[1.7.11].
206 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
209 link:RelNotes/1.7.10.5.txt[1.7.10.5],
210 link:RelNotes/1.7.10.4.txt[1.7.10.4],
211 link:RelNotes/1.7.10.3.txt[1.7.10.3],
212 link:RelNotes/1.7.10.2.txt[1.7.10.2],
213 link:RelNotes/1.7.10.1.txt[1.7.10.1],
214 link:RelNotes/1.7.10.txt[1.7.10].
216 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
219 link:RelNotes/1.7.9.7.txt[1.7.9.7],
220 link:RelNotes/1.7.9.6.txt[1.7.9.6],
221 link:RelNotes/1.7.9.5.txt[1.7.9.5],
222 link:RelNotes/1.7.9.4.txt[1.7.9.4],
223 link:RelNotes/1.7.9.3.txt[1.7.9.3],
224 link:RelNotes/1.7.9.2.txt[1.7.9.2],
225 link:RelNotes/1.7.9.1.txt[1.7.9.1],
226 link:RelNotes/1.7.9.txt[1.7.9].
228 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
231 link:RelNotes/1.7.8.6.txt[1.7.8.6],
232 link:RelNotes/1.7.8.5.txt[1.7.8.5],
233 link:RelNotes/1.7.8.4.txt[1.7.8.4],
234 link:RelNotes/1.7.8.3.txt[1.7.8.3],
235 link:RelNotes/1.7.8.2.txt[1.7.8.2],
236 link:RelNotes/1.7.8.1.txt[1.7.8.1],
237 link:RelNotes/1.7.8.txt[1.7.8].
239 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
242 link:RelNotes/1.7.7.7.txt[1.7.7.7],
243 link:RelNotes/1.7.7.6.txt[1.7.7.6],
244 link:RelNotes/1.7.7.5.txt[1.7.7.5],
245 link:RelNotes/1.7.7.4.txt[1.7.7.4],
246 link:RelNotes/1.7.7.3.txt[1.7.7.3],
247 link:RelNotes/1.7.7.2.txt[1.7.7.2],
248 link:RelNotes/1.7.7.1.txt[1.7.7.1],
249 link:RelNotes/1.7.7.txt[1.7.7].
251 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
254 link:RelNotes/1.7.6.6.txt[1.7.6.6],
255 link:RelNotes/1.7.6.5.txt[1.7.6.5],
256 link:RelNotes/1.7.6.4.txt[1.7.6.4],
257 link:RelNotes/1.7.6.3.txt[1.7.6.3],
258 link:RelNotes/1.7.6.2.txt[1.7.6.2],
259 link:RelNotes/1.7.6.1.txt[1.7.6.1],
260 link:RelNotes/1.7.6.txt[1.7.6].
262 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
265 link:RelNotes/1.7.5.4.txt[1.7.5.4],
266 link:RelNotes/1.7.5.3.txt[1.7.5.3],
267 link:RelNotes/1.7.5.2.txt[1.7.5.2],
268 link:RelNotes/1.7.5.1.txt[1.7.5.1],
269 link:RelNotes/1.7.5.txt[1.7.5].
271 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
274 link:RelNotes/1.7.4.5.txt[1.7.4.5],
275 link:RelNotes/1.7.4.4.txt[1.7.4.4],
276 link:RelNotes/1.7.4.3.txt[1.7.4.3],
277 link:RelNotes/1.7.4.2.txt[1.7.4.2],
278 link:RelNotes/1.7.4.1.txt[1.7.4.1],
279 link:RelNotes/1.7.4.txt[1.7.4].
281 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
284 link:RelNotes/1.7.3.5.txt[1.7.3.5],
285 link:RelNotes/1.7.3.4.txt[1.7.3.4],
286 link:RelNotes/1.7.3.3.txt[1.7.3.3],
287 link:RelNotes/1.7.3.2.txt[1.7.3.2],
288 link:RelNotes/1.7.3.1.txt[1.7.3.1],
289 link:RelNotes/1.7.3.txt[1.7.3].
291 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
294 link:RelNotes/1.7.2.5.txt[1.7.2.5],
295 link:RelNotes/1.7.2.4.txt[1.7.2.4],
296 link:RelNotes/1.7.2.3.txt[1.7.2.3],
297 link:RelNotes/1.7.2.2.txt[1.7.2.2],
298 link:RelNotes/1.7.2.1.txt[1.7.2.1],
299 link:RelNotes/1.7.2.txt[1.7.2].
301 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
304 link:RelNotes/1.7.1.4.txt[1.7.1.4],
305 link:RelNotes/1.7.1.3.txt[1.7.1.3],
306 link:RelNotes/1.7.1.2.txt[1.7.1.2],
307 link:RelNotes/1.7.1.1.txt[1.7.1.1],
308 link:RelNotes/1.7.1.txt[1.7.1].
310 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
313 link:RelNotes/1.7.0.9.txt[1.7.0.9],
314 link:RelNotes/1.7.0.8.txt[1.7.0.8],
315 link:RelNotes/1.7.0.7.txt[1.7.0.7],
316 link:RelNotes/1.7.0.6.txt[1.7.0.6],
317 link:RelNotes/1.7.0.5.txt[1.7.0.5],
318 link:RelNotes/1.7.0.4.txt[1.7.0.4],
319 link:RelNotes/1.7.0.3.txt[1.7.0.3],
320 link:RelNotes/1.7.0.2.txt[1.7.0.2],
321 link:RelNotes/1.7.0.1.txt[1.7.0.1],
322 link:RelNotes/1.7.0.txt[1.7.0].
324 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
327 link:RelNotes/1.6.6.3.txt[1.6.6.3],
328 link:RelNotes/1.6.6.2.txt[1.6.6.2],
329 link:RelNotes/1.6.6.1.txt[1.6.6.1],
330 link:RelNotes/1.6.6.txt[1.6.6].
332 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
335 link:RelNotes/1.6.5.9.txt[1.6.5.9],
336 link:RelNotes/1.6.5.8.txt[1.6.5.8],
337 link:RelNotes/1.6.5.7.txt[1.6.5.7],
338 link:RelNotes/1.6.5.6.txt[1.6.5.6],
339 link:RelNotes/1.6.5.5.txt[1.6.5.5],
340 link:RelNotes/1.6.5.4.txt[1.6.5.4],
341 link:RelNotes/1.6.5.3.txt[1.6.5.3],
342 link:RelNotes/1.6.5.2.txt[1.6.5.2],
343 link:RelNotes/1.6.5.1.txt[1.6.5.1],
344 link:RelNotes/1.6.5.txt[1.6.5].
346 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
349 link:RelNotes/1.6.4.5.txt[1.6.4.5],
350 link:RelNotes/1.6.4.4.txt[1.6.4.4],
351 link:RelNotes/1.6.4.3.txt[1.6.4.3],
352 link:RelNotes/1.6.4.2.txt[1.6.4.2],
353 link:RelNotes/1.6.4.1.txt[1.6.4.1],
354 link:RelNotes/1.6.4.txt[1.6.4].
356 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
359 link:RelNotes/1.6.3.4.txt[1.6.3.4],
360 link:RelNotes/1.6.3.3.txt[1.6.3.3],
361 link:RelNotes/1.6.3.2.txt[1.6.3.2],
362 link:RelNotes/1.6.3.1.txt[1.6.3.1],
363 link:RelNotes/1.6.3.txt[1.6.3].
366 link:RelNotes/1.6.2.5.txt[1.6.2.5],
367 link:RelNotes/1.6.2.4.txt[1.6.2.4],
368 link:RelNotes/1.6.2.3.txt[1.6.2.3],
369 link:RelNotes/1.6.2.2.txt[1.6.2.2],
370 link:RelNotes/1.6.2.1.txt[1.6.2.1],
371 link:RelNotes/1.6.2.txt[1.6.2].
373 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
376 link:RelNotes/1.6.1.3.txt[1.6.1.3],
377 link:RelNotes/1.6.1.2.txt[1.6.1.2],
378 link:RelNotes/1.6.1.1.txt[1.6.1.1],
379 link:RelNotes/1.6.1.txt[1.6.1].
381 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
384 link:RelNotes/1.6.0.6.txt[1.6.0.6],
385 link:RelNotes/1.6.0.5.txt[1.6.0.5],
386 link:RelNotes/1.6.0.4.txt[1.6.0.4],
387 link:RelNotes/1.6.0.3.txt[1.6.0.3],
388 link:RelNotes/1.6.0.2.txt[1.6.0.2],
389 link:RelNotes/1.6.0.1.txt[1.6.0.1],
390 link:RelNotes/1.6.0.txt[1.6.0].
392 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
395 link:RelNotes/1.5.6.6.txt[1.5.6.6],
396 link:RelNotes/1.5.6.5.txt[1.5.6.5],
397 link:RelNotes/1.5.6.4.txt[1.5.6.4],
398 link:RelNotes/1.5.6.3.txt[1.5.6.3],
399 link:RelNotes/1.5.6.2.txt[1.5.6.2],
400 link:RelNotes/1.5.6.1.txt[1.5.6.1],
401 link:RelNotes/1.5.6.txt[1.5.6].
403 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
406 link:RelNotes/1.5.5.6.txt[1.5.5.6],
407 link:RelNotes/1.5.5.5.txt[1.5.5.5],
408 link:RelNotes/1.5.5.4.txt[1.5.5.4],
409 link:RelNotes/1.5.5.3.txt[1.5.5.3],
410 link:RelNotes/1.5.5.2.txt[1.5.5.2],
411 link:RelNotes/1.5.5.1.txt[1.5.5.1],
412 link:RelNotes/1.5.5.txt[1.5.5].
414 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
417 link:RelNotes/1.5.4.7.txt[1.5.4.7],
418 link:RelNotes/1.5.4.6.txt[1.5.4.6],
419 link:RelNotes/1.5.4.5.txt[1.5.4.5],
420 link:RelNotes/1.5.4.4.txt[1.5.4.4],
421 link:RelNotes/1.5.4.3.txt[1.5.4.3],
422 link:RelNotes/1.5.4.2.txt[1.5.4.2],
423 link:RelNotes/1.5.4.1.txt[1.5.4.1],
424 link:RelNotes/1.5.4.txt[1.5.4].
426 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
429 link:RelNotes/1.5.3.8.txt[1.5.3.8],
430 link:RelNotes/1.5.3.7.txt[1.5.3.7],
431 link:RelNotes/1.5.3.6.txt[1.5.3.6],
432 link:RelNotes/1.5.3.5.txt[1.5.3.5],
433 link:RelNotes/1.5.3.4.txt[1.5.3.4],
434 link:RelNotes/1.5.3.3.txt[1.5.3.3],
435 link:RelNotes/1.5.3.2.txt[1.5.3.2],
436 link:RelNotes/1.5.3.1.txt[1.5.3.1],
437 link:RelNotes/1.5.3.txt[1.5.3].
439 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
442 link:RelNotes/1.5.2.5.txt[1.5.2.5],
443 link:RelNotes/1.5.2.4.txt[1.5.2.4],
444 link:RelNotes/1.5.2.3.txt[1.5.2.3],
445 link:RelNotes/1.5.2.2.txt[1.5.2.2],
446 link:RelNotes/1.5.2.1.txt[1.5.2.1],
447 link:RelNotes/1.5.2.txt[1.5.2].
449 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
452 link:RelNotes/1.5.1.6.txt[1.5.1.6],
453 link:RelNotes/1.5.1.5.txt[1.5.1.5],
454 link:RelNotes/1.5.1.4.txt[1.5.1.4],
455 link:RelNotes/1.5.1.3.txt[1.5.1.3],
456 link:RelNotes/1.5.1.2.txt[1.5.1.2],
457 link:RelNotes/1.5.1.1.txt[1.5.1.1],
458 link:RelNotes/1.5.1.txt[1.5.1].
460 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
463 link:RelNotes/1.5.0.7.txt[1.5.0.7],
464 link:RelNotes/1.5.0.6.txt[1.5.0.6],
465 link:RelNotes/1.5.0.5.txt[1.5.0.5],
466 link:RelNotes/1.5.0.3.txt[1.5.0.3],
467 link:RelNotes/1.5.0.2.txt[1.5.0.2],
468 link:RelNotes/1.5.0.1.txt[1.5.0.1],
469 link:RelNotes/1.5.0.txt[1.5.0].
471 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
472 link:v1.3.3/git.html[1.3.3],
473 link:v1.2.6/git.html[1.2.6],
474 link:v1.0.13/git.html[1.0.13].
483 Prints the Git suite version that the 'git' program came from.
486 Prints the synopsis and a list of the most commonly used
487 commands. If the option '--all' or '-a' is given then all
488 available commands are printed. If a Git command is named this
489 option will bring up the manual page for that command.
491 Other options are available to control how the manual page is
492 displayed. See linkgit:git-help[1] for more information,
493 because `git --help ...` is converted internally into `git
497 Run as if git was started in '<path>' instead of the current working
498 directory. When multiple `-C` options are given, each subsequent
499 non-absolute `-C <path>` is interpreted relative to the preceding `-C
502 This option affects options that expect path name like `--git-dir` and
503 `--work-tree` in that their interpretations of the path names would be
504 made relative to the working directory caused by the `-C` option. For
505 example the following invocations are equivalent:
507 git --git-dir=a.git --work-tree=b -C c status
508 git --git-dir=c/a.git --work-tree=c/b status
511 Pass a configuration parameter to the command. The value
512 given will override values from configuration files.
513 The <name> is expected in the same format as listed by
514 'git config' (subkeys separated by dots).
516 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
517 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
518 config file). Including the equals but with an empty value (like `git -c
519 foo.bar= ...`) sets `foo.bar` to the empty string.
521 --exec-path[=<path>]::
522 Path to wherever your core Git programs are installed.
523 This can also be controlled by setting the GIT_EXEC_PATH
524 environment variable. If no path is given, 'git' will print
525 the current setting and then exit.
528 Print the path, without trailing slash, where Git's HTML
529 documentation is installed and exit.
532 Print the manpath (see `man(1)`) for the man pages for
533 this version of Git and exit.
536 Print the path where the Info files documenting this
537 version of Git are installed and exit.
541 Pipe all output into 'less' (or if set, $PAGER) if standard
542 output is a terminal. This overrides the `pager.<cmd>`
543 configuration options (see the "Configuration Mechanism" section
547 Do not pipe Git output into a pager.
550 Set the path to the repository. This can also be controlled by
551 setting the GIT_DIR environment variable. It can be an absolute
552 path or relative path to current working directory.
555 Set the path to the working tree. It can be an absolute path
556 or a path relative to the current working directory.
557 This can also be controlled by setting the GIT_WORK_TREE
558 environment variable and the core.worktree configuration
559 variable (see core.worktree in linkgit:git-config[1] for a
560 more detailed discussion).
563 Set the Git namespace. See linkgit:gitnamespaces[7] for more
564 details. Equivalent to setting the `GIT_NAMESPACE` environment
568 Treat the repository as a bare repository. If GIT_DIR
569 environment is not set, it is set to the current working
572 --no-replace-objects::
573 Do not use replacement refs to replace Git objects. See
574 linkgit:git-replace[1] for more information.
576 --literal-pathspecs::
577 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
578 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
582 Add "glob" magic to all pathspec. This is equivalent to setting
583 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
584 globbing on individual pathspecs can be done using pathspec
588 Add "literal" magic to all pathspec. This is equivalent to setting
589 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
590 globbing on individual pathspecs can be done using pathspec
594 Add "icase" magic to all pathspec. This is equivalent to setting
595 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
600 We divide Git into high level ("porcelain") commands and low level
601 ("plumbing") commands.
603 High-level commands (porcelain)
604 -------------------------------
606 We separate the porcelain commands into the main commands and some
607 ancillary user utilities.
609 Main porcelain commands
610 ~~~~~~~~~~~~~~~~~~~~~~~
612 include::cmds-mainporcelain.txt[]
618 include::cmds-ancillarymanipulators.txt[]
622 include::cmds-ancillaryinterrogators.txt[]
625 Interacting with Others
626 ~~~~~~~~~~~~~~~~~~~~~~~
628 These commands are to interact with foreign SCM and with other
629 people via patch over e-mail.
631 include::cmds-foreignscminterface.txt[]
634 Low-level commands (plumbing)
635 -----------------------------
637 Although Git includes its
638 own porcelain layer, its low-level commands are sufficient to support
639 development of alternative porcelains. Developers of such porcelains
640 might start by reading about linkgit:git-update-index[1] and
641 linkgit:git-read-tree[1].
643 The interface (input, output, set of options and the semantics)
644 to these low-level commands are meant to be a lot more stable
645 than Porcelain level commands, because these commands are
646 primarily for scripted use. The interface to Porcelain commands
647 on the other hand are subject to change in order to improve the
650 The following description divides
651 the low-level commands into commands that manipulate objects (in
652 the repository, index, and working tree), commands that interrogate and
653 compare objects, and commands that move objects and references between
657 Manipulation commands
658 ~~~~~~~~~~~~~~~~~~~~~
660 include::cmds-plumbingmanipulators.txt[]
663 Interrogation commands
664 ~~~~~~~~~~~~~~~~~~~~~~
666 include::cmds-plumbinginterrogators.txt[]
668 In general, the interrogate commands do not touch the files in
672 Synching repositories
673 ~~~~~~~~~~~~~~~~~~~~~
675 include::cmds-synchingrepositories.txt[]
677 The following are helper commands used by the above; end users
678 typically do not use them directly.
680 include::cmds-synchelpers.txt[]
683 Internal helper commands
684 ~~~~~~~~~~~~~~~~~~~~~~~~
686 These are internal helper commands used by other commands; end
687 users typically do not use them directly.
689 include::cmds-purehelpers.txt[]
692 Configuration Mechanism
693 -----------------------
695 Git uses a simple text format to store customizations that are per
696 repository and are per user. Such a configuration file may look
701 # A '#' or ';' character indicates a comment.
706 ; Don't trust file modes
711 name = "Junio C Hamano"
712 email = "gitster@pobox.com"
716 Various commands read from the configuration file and adjust
717 their operation accordingly. See linkgit:git-config[1] for a
718 list and more details about the configuration mechanism.
721 Identifier Terminology
722 ----------------------
724 Indicates the object name for any type of object.
727 Indicates a blob object name.
730 Indicates a tree object name.
733 Indicates a commit object name.
736 Indicates a tree, commit or tag object name. A
737 command that takes a <tree-ish> argument ultimately wants to
738 operate on a <tree> object but automatically dereferences
739 <commit> and <tag> objects that point at a <tree>.
742 Indicates a commit or tag object name. A
743 command that takes a <commit-ish> argument ultimately wants to
744 operate on a <commit> object but automatically dereferences
745 <tag> objects that point at a <commit>.
748 Indicates that an object type is required.
749 Currently one of: `blob`, `tree`, `commit`, or `tag`.
752 Indicates a filename - almost always relative to the
753 root of the tree structure `GIT_INDEX_FILE` describes.
757 Any Git command accepting any <object> can also use the following
761 indicates the head of the current branch.
765 (i.e. a `refs/tags/<tag>` reference).
769 (i.e. a `refs/heads/<head>` reference).
771 For a more complete list of ways to spell object names, see
772 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
775 File/Directory Structure
776 ------------------------
778 Please see the linkgit:gitrepository-layout[5] document.
780 Read linkgit:githooks[5] for more details about each hook.
782 Higher level SCMs may provide and manage additional information in the
788 Please see linkgit:gitglossary[7].
791 Environment Variables
792 ---------------------
793 Various Git commands use the following environment variables:
797 These environment variables apply to 'all' core Git commands. Nb: it
798 is worth noting that they may be used/overridden by SCMS sitting above
799 Git so take care if using a foreign front-end.
802 This environment allows the specification of an alternate
803 index file. If not specified, the default of `$GIT_DIR/index`
806 'GIT_INDEX_VERSION'::
807 This environment variable allows the specification of an index
808 version for new repositories. It won't affect existing index
809 files. By default index file version 2 or 3 is used. See
810 linkgit:git-update-index[1] for more information.
812 'GIT_OBJECT_DIRECTORY'::
813 If the object storage directory is specified via this
814 environment variable then the sha1 directories are created
815 underneath - otherwise the default `$GIT_DIR/objects`
818 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
819 Due to the immutable nature of Git objects, old objects can be
820 archived into shared, read-only directories. This variable
821 specifies a ":" separated (on Windows ";" separated) list
822 of Git object directories which can be used to search for Git
823 objects. New objects will not be written to these directories.
826 If the 'GIT_DIR' environment variable is set then it
827 specifies a path to use instead of the default `.git`
828 for the base of the repository.
829 The '--git-dir' command-line option also sets this value.
832 Set the path to the root of the working tree.
833 This can also be controlled by the '--work-tree' command-line
834 option and the core.worktree configuration variable.
837 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
838 The '--namespace' command-line option also sets this value.
840 'GIT_CEILING_DIRECTORIES'::
841 This should be a colon-separated list of absolute paths. If
842 set, it is a list of directories that Git should not chdir up
843 into while looking for a repository directory (useful for
844 excluding slow-loading network directories). It will not
845 exclude the current working directory or a GIT_DIR set on the
846 command line or in the environment. Normally, Git has to read
847 the entries in this list and resolve any symlink that
848 might be present in order to compare them with the current
849 directory. However, if even this access is slow, you
850 can add an empty entry to the list to tell Git that the
851 subsequent entries are not symlinks and needn't be resolved;
853 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
855 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
856 When run in a directory that does not have ".git" repository
857 directory, Git tries to find such a directory in the parent
858 directories to find the top of the working tree, but by default it
859 does not cross filesystem boundaries. This environment variable
860 can be set to true to tell Git not to stop at filesystem
861 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
862 an explicit repository directory set via 'GIT_DIR' or on the
866 If this variable is set to a path, non-worktree files that are
867 normally in $GIT_DIR will be taken from this path
868 instead. Worktree-specific files such as HEAD or index are
869 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
870 linkgit:git-worktree[1] for
871 details. This variable has lower precedence than other path
872 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
879 'GIT_COMMITTER_NAME'::
880 'GIT_COMMITTER_EMAIL'::
881 'GIT_COMMITTER_DATE'::
883 see linkgit:git-commit-tree[1]
888 Only valid setting is "--unified=??" or "-u??" to set the
889 number of context lines shown when a unified diff is created.
890 This takes precedence over any "-U" or "--unified" option
891 value passed on the Git diff command line.
893 'GIT_EXTERNAL_DIFF'::
894 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
895 program named by it is called, instead of the diff invocation
896 described above. For a path that is added, removed, or modified,
897 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
899 path old-file old-hex old-mode new-file new-hex new-mode
903 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
904 contents of <old|new>,
905 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
906 <old|new>-mode:: are the octal representation of the file modes.
908 The file parameters can point at the user's working file
909 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
910 when a new file is added), or a temporary file (e.g. `old-file` in the
911 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
912 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
914 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
917 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
918 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
920 'GIT_DIFF_PATH_COUNTER'::
921 A 1-based counter incremented by one for every path.
923 'GIT_DIFF_PATH_TOTAL'::
924 The total number of paths.
928 'GIT_MERGE_VERBOSITY'::
929 A number controlling the amount of output shown by
930 the recursive merge strategy. Overrides merge.verbosity.
931 See linkgit:git-merge[1]
934 This environment variable overrides `$PAGER`. If it is set
935 to an empty string or to the value "cat", Git will not launch
936 a pager. See also the `core.pager` option in
937 linkgit:git-config[1].
940 This environment variable overrides `$EDITOR` and `$VISUAL`.
941 It is used by several Git commands when, on interactive mode,
942 an editor is to be launched. See also linkgit:git-var[1]
943 and the `core.editor` option in linkgit:git-config[1].
947 If either of these environment variables is set then 'git fetch'
948 and 'git push' will use the specified command instead of 'ssh'
949 when they need to connect to a remote system.
950 The command will be given exactly two or four arguments: the
951 'username@host' (or just 'host') from the URL and the shell
952 command to execute on that remote system, optionally preceded by
953 '-p' (literally) and the 'port' from the URL when it specifies
954 something other than the default SSH port.
956 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
957 by the shell, which allows additional arguments to be included.
958 `$GIT_SSH` on the other hand must be just the path to a program
959 (which can be a wrapper shell script, if additional arguments are
962 Usually it is easier to configure any desired options through your
963 personal `.ssh/config` file. Please consult your ssh documentation
967 If this environment variable is set, then Git commands which need to
968 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
969 will call this program with a suitable prompt as command-line argument
970 and read the password from its STDOUT. See also the 'core.askPass'
971 option in linkgit:git-config[1].
973 'GIT_TERMINAL_PROMPT'::
974 If this environment variable is set to `0`, git will not prompt
975 on the terminal (e.g., when asking for HTTP authentication).
977 'GIT_CONFIG_NOSYSTEM'::
978 Whether to skip reading settings from the system-wide
979 `$(prefix)/etc/gitconfig` file. This environment variable can
980 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
981 predictable environment for a picky script, or you can set it
982 temporarily to avoid using a buggy `/etc/gitconfig` file while
983 waiting for someone with sufficient permissions to fix it.
986 If this environment variable is set to "1", then commands such
987 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
988 'git check-attr' and 'git check-ignore' will
989 force a flush of the output stream after each record have been
991 variable is set to "0", the output of these commands will be done
992 using completely buffered I/O. If this environment variable is
993 not set, Git will choose buffered or record-oriented flushing
994 based on whether stdout appears to be redirected to a file or not.
997 Enables general trace messages, e.g. alias expansion, built-in
998 command execution and external command execution.
1000 If this variable is set to "1", "2" or "true" (comparison
1001 is case insensitive), trace messages will be printed to
1004 If the variable is set to an integer value greater than 2
1005 and lower than 10 (strictly) then Git will interpret this
1006 value as an open file descriptor and will try to write the
1007 trace messages into this file descriptor.
1009 Alternatively, if the variable is set to an absolute path
1010 (starting with a '/' character), Git will interpret this
1011 as a file path and will try to write the trace messages
1014 Unsetting the variable, or setting it to empty, "0" or
1015 "false" (case insensitive) disables trace messages.
1017 'GIT_TRACE_PACK_ACCESS'::
1018 Enables trace messages for all accesses to any packs. For each
1019 access, the pack file name and an offset in the pack is
1020 recorded. This may be helpful for troubleshooting some
1021 pack-related performance problems.
1022 See 'GIT_TRACE' for available trace output options.
1024 'GIT_TRACE_PACKET'::
1025 Enables trace messages for all packets coming in or out of a
1026 given program. This can help with debugging object negotiation
1027 or other protocol issues. Tracing is turned off at a packet
1028 starting with "PACK" (but see 'GIT_TRACE_PACKFILE' below).
1029 See 'GIT_TRACE' for available trace output options.
1031 'GIT_TRACE_PACKFILE'::
1032 Enables tracing of packfiles sent or received by a
1033 given program. Unlike other trace output, this trace is
1034 verbatim: no headers, and no quoting of binary data. You almost
1035 certainly want to direct into a file (e.g.,
1036 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1037 the terminal or mixing it with other trace output.
1039 Note that this is currently only implemented for the client side
1040 of clones and fetches.
1042 'GIT_TRACE_PERFORMANCE'::
1043 Enables performance related trace messages, e.g. total execution
1044 time of each Git command.
1045 See 'GIT_TRACE' for available trace output options.
1048 Enables trace messages printing the .git, working tree and current
1049 working directory after Git has completed its setup phase.
1050 See 'GIT_TRACE' for available trace output options.
1052 'GIT_TRACE_SHALLOW'::
1053 Enables trace messages that can help debugging fetching /
1054 cloning of shallow repositories.
1055 See 'GIT_TRACE' for available trace output options.
1057 GIT_LITERAL_PATHSPECS::
1058 Setting this variable to `1` will cause Git to treat all
1059 pathspecs literally, rather than as glob patterns. For example,
1060 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1061 for commits that touch the path `*.c`, not any paths that the
1062 glob `*.c` matches. You might want this if you are feeding
1063 literal paths to Git (e.g., paths previously given to you by
1064 `git ls-tree`, `--raw` diff output, etc).
1066 GIT_GLOB_PATHSPECS::
1067 Setting this variable to `1` will cause Git to treat all
1068 pathspecs as glob patterns (aka "glob" magic).
1070 GIT_NOGLOB_PATHSPECS::
1071 Setting this variable to `1` will cause Git to treat all
1072 pathspecs as literal (aka "literal" magic).
1074 GIT_ICASE_PATHSPECS::
1075 Setting this variable to `1` will cause Git to treat all
1076 pathspecs as case-insensitive.
1078 'GIT_REFLOG_ACTION'::
1079 When a ref is updated, reflog entries are created to keep
1080 track of the reason why the ref was updated (which is
1081 typically the name of the high-level command that updated
1082 the ref), in addition to the old and new values of the ref.
1083 A scripted Porcelain command can use set_reflog_action
1084 helper function in `git-sh-setup` to set its name to this
1085 variable when it is invoked as the top level command by the
1086 end user, to be recorded in the body of the reflog.
1088 `GIT_REF_PARANOIA`::
1089 If set to `1`, include broken or badly named refs when iterating
1090 over lists of refs. In a normal, non-corrupted repository, this
1091 does nothing. However, enabling it may help git to detect and
1092 abort some operations in the presence of broken refs. Git sets
1093 this variable automatically when performing destructive
1094 operations like linkgit:git-prune[1]. You should not need to set
1095 it yourself unless you want to be paranoid about making sure
1096 an operation has touched every ref (e.g., because you are
1097 cloning a repository to make a backup).
1099 `GIT_ALLOW_PROTOCOL`::
1100 If set, provide a colon-separated list of protocols which are
1101 allowed to be used with fetch/push/clone. This is useful to
1102 restrict recursive submodule initialization from an untrusted
1103 repository. Any protocol not mentioned will be disallowed (i.e.,
1104 this is a whitelist, not a blacklist). If the variable is not
1105 set at all, all protocols are enabled. The protocol names
1106 currently used by git are:
1108 - `file`: any local file-based path (including `file://` URLs,
1111 - `git`: the anonymous git protocol over a direct TCP
1112 connection (or proxy, if configured)
1114 - `ssh`: git over ssh (including `host:path` syntax,
1117 - `rsync`: git over rsync
1119 - `http`: git over http, both "smart http" and "dumb http".
1120 Note that this does _not_ include `https`; if you want both,
1121 you should specify both as `http:https`.
1123 - any external helpers are named by their protocol (e.g., use
1124 `hg` to allow the `git-remote-hg` helper)
1127 Discussion[[Discussion]]
1128 ------------------------
1130 More detail on the following is available from the
1131 link:user-manual.html#git-concepts[Git concepts chapter of the
1132 user-manual] and linkgit:gitcore-tutorial[7].
1134 A Git project normally consists of a working directory with a ".git"
1135 subdirectory at the top level. The .git directory contains, among other
1136 things, a compressed object database representing the complete history
1137 of the project, an "index" file which links that history to the current
1138 contents of the working tree, and named pointers into that history such
1139 as tags and branch heads.
1141 The object database contains objects of three main types: blobs, which
1142 hold file data; trees, which point to blobs and other trees to build up
1143 directory hierarchies; and commits, which each reference a single tree
1144 and some number of parent commits.
1146 The commit, equivalent to what other systems call a "changeset" or
1147 "version", represents a step in the project's history, and each parent
1148 represents an immediately preceding step. Commits with more than one
1149 parent represent merges of independent lines of development.
1151 All objects are named by the SHA-1 hash of their contents, normally
1152 written as a string of 40 hex digits. Such names are globally unique.
1153 The entire history leading up to a commit can be vouched for by signing
1154 just that commit. A fourth object type, the tag, is provided for this
1157 When first created, objects are stored in individual files, but for
1158 efficiency may later be compressed together into "pack files".
1160 Named pointers called refs mark interesting points in history. A ref
1161 may contain the SHA-1 name of an object or the name of another ref. Refs
1162 with names beginning `ref/head/` contain the SHA-1 name of the most
1163 recent commit (or "head") of a branch under development. SHA-1 names of
1164 tags of interest are stored under `ref/tags/`. A special ref named
1165 `HEAD` contains the name of the currently checked-out branch.
1167 The index file is initialized with a list of all paths and, for each
1168 path, a blob object and a set of attributes. The blob object represents
1169 the contents of the file as of the head of the current branch. The
1170 attributes (last modified time, size, etc.) are taken from the
1171 corresponding file in the working tree. Subsequent changes to the
1172 working tree can be found by comparing these attributes. The index may
1173 be updated with new content, and new commits may be created from the
1174 content stored in the index.
1176 The index is also capable of storing multiple entries (called "stages")
1177 for a given pathname. These stages are used to hold the various
1178 unmerged version of a file when a merge is in progress.
1180 FURTHER DOCUMENTATION
1181 ---------------------
1183 See the references in the "description" section to get started
1184 using Git. The following is probably more detail than necessary
1185 for a first-time user.
1187 The link:user-manual.html#git-concepts[Git concepts chapter of the
1188 user-manual] and linkgit:gitcore-tutorial[7] both provide
1189 introductions to the underlying Git architecture.
1191 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1193 See also the link:howto-index.html[howto] documents for some useful
1196 The internals are documented in the
1197 link:technical/api-index.html[Git API documentation].
1199 Users migrating from CVS may also want to
1200 read linkgit:gitcvs-migration[7].
1205 Git was started by Linus Torvalds, and is currently maintained by Junio
1206 C Hamano. Numerous contributions have come from the Git mailing list
1207 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1208 gives you a more complete list of contributors.
1210 If you have a clone of git.git itself, the
1211 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1212 the authors for specific parts of the project.
1217 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1218 development and maintenance is primarily done. You do not have to be
1219 subscribed to the list to send a message there.
1223 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1224 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1225 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1226 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1227 linkgit:gitworkflows[7]
1231 Part of the linkgit:git[1] suite