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.2/git.html[documentation for release 2.6.2]
49 link:RelNotes/2.6.2.txt[2.6.2],
50 link:RelNotes/2.6.1.txt[2.6.1],
51 link:RelNotes/2.6.0.txt[2.6].
53 * link:v2.5.4/git.html[documentation for release 2.5.4]
56 link:RelNotes/2.5.4.txt[2.5.4],
57 link:RelNotes/2.5.3.txt[2.5.3],
58 link:RelNotes/2.5.2.txt[2.5.2],
59 link:RelNotes/2.5.1.txt[2.5.1],
60 link:RelNotes/2.5.0.txt[2.5].
62 * link:v2.4.10/git.html[documentation for release 2.4.10]
65 link:RelNotes/2.4.10.txt[2.4.10],
66 link:RelNotes/2.4.9.txt[2.4.9],
67 link:RelNotes/2.4.8.txt[2.4.8],
68 link:RelNotes/2.4.7.txt[2.4.7],
69 link:RelNotes/2.4.6.txt[2.4.6],
70 link:RelNotes/2.4.5.txt[2.4.5],
71 link:RelNotes/2.4.4.txt[2.4.4],
72 link:RelNotes/2.4.3.txt[2.4.3],
73 link:RelNotes/2.4.2.txt[2.4.2],
74 link:RelNotes/2.4.1.txt[2.4.1],
75 link:RelNotes/2.4.0.txt[2.4].
77 * link:v2.3.10/git.html[documentation for release 2.3.10]
80 link:RelNotes/2.3.10.txt[2.3.10],
81 link:RelNotes/2.3.9.txt[2.3.9],
82 link:RelNotes/2.3.8.txt[2.3.8],
83 link:RelNotes/2.3.7.txt[2.3.7],
84 link:RelNotes/2.3.6.txt[2.3.6],
85 link:RelNotes/2.3.5.txt[2.3.5],
86 link:RelNotes/2.3.4.txt[2.3.4],
87 link:RelNotes/2.3.3.txt[2.3.3],
88 link:RelNotes/2.3.2.txt[2.3.2],
89 link:RelNotes/2.3.1.txt[2.3.1],
90 link:RelNotes/2.3.0.txt[2.3].
92 * link:v2.2.3/git.html[documentation for release 2.2.3]
95 link:RelNotes/2.2.3.txt[2.2.3],
96 link:RelNotes/2.2.2.txt[2.2.2],
97 link:RelNotes/2.2.1.txt[2.2.1],
98 link:RelNotes/2.2.0.txt[2.2].
100 * link:v2.1.4/git.html[documentation for release 2.1.4]
103 link:RelNotes/2.1.4.txt[2.1.4],
104 link:RelNotes/2.1.3.txt[2.1.3],
105 link:RelNotes/2.1.2.txt[2.1.2],
106 link:RelNotes/2.1.1.txt[2.1.1],
107 link:RelNotes/2.1.0.txt[2.1].
109 * link:v2.0.5/git.html[documentation for release 2.0.5]
112 link:RelNotes/2.0.5.txt[2.0.5],
113 link:RelNotes/2.0.4.txt[2.0.4],
114 link:RelNotes/2.0.3.txt[2.0.3],
115 link:RelNotes/2.0.2.txt[2.0.2],
116 link:RelNotes/2.0.1.txt[2.0.1],
117 link:RelNotes/2.0.0.txt[2.0.0].
119 * link:v1.9.5/git.html[documentation for release 1.9.5]
122 link:RelNotes/1.9.5.txt[1.9.5],
123 link:RelNotes/1.9.4.txt[1.9.4],
124 link:RelNotes/1.9.3.txt[1.9.3],
125 link:RelNotes/1.9.2.txt[1.9.2],
126 link:RelNotes/1.9.1.txt[1.9.1],
127 link:RelNotes/1.9.0.txt[1.9.0].
129 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
132 link:RelNotes/1.8.5.6.txt[1.8.5.6],
133 link:RelNotes/1.8.5.5.txt[1.8.5.5],
134 link:RelNotes/1.8.5.4.txt[1.8.5.4],
135 link:RelNotes/1.8.5.3.txt[1.8.5.3],
136 link:RelNotes/1.8.5.2.txt[1.8.5.2],
137 link:RelNotes/1.8.5.1.txt[1.8.5.1],
138 link:RelNotes/1.8.5.txt[1.8.5].
140 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
143 link:RelNotes/1.8.4.5.txt[1.8.4.5],
144 link:RelNotes/1.8.4.4.txt[1.8.4.4],
145 link:RelNotes/1.8.4.3.txt[1.8.4.3],
146 link:RelNotes/1.8.4.2.txt[1.8.4.2],
147 link:RelNotes/1.8.4.1.txt[1.8.4.1],
148 link:RelNotes/1.8.4.txt[1.8.4].
150 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
153 link:RelNotes/1.8.3.4.txt[1.8.3.4],
154 link:RelNotes/1.8.3.3.txt[1.8.3.3],
155 link:RelNotes/1.8.3.2.txt[1.8.3.2],
156 link:RelNotes/1.8.3.1.txt[1.8.3.1],
157 link:RelNotes/1.8.3.txt[1.8.3].
159 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
162 link:RelNotes/1.8.2.3.txt[1.8.2.3],
163 link:RelNotes/1.8.2.2.txt[1.8.2.2],
164 link:RelNotes/1.8.2.1.txt[1.8.2.1],
165 link:RelNotes/1.8.2.txt[1.8.2].
167 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
170 link:RelNotes/1.8.1.6.txt[1.8.1.6],
171 link:RelNotes/1.8.1.5.txt[1.8.1.5],
172 link:RelNotes/1.8.1.4.txt[1.8.1.4],
173 link:RelNotes/1.8.1.3.txt[1.8.1.3],
174 link:RelNotes/1.8.1.2.txt[1.8.1.2],
175 link:RelNotes/1.8.1.1.txt[1.8.1.1],
176 link:RelNotes/1.8.1.txt[1.8.1].
178 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
181 link:RelNotes/1.8.0.3.txt[1.8.0.3],
182 link:RelNotes/1.8.0.2.txt[1.8.0.2],
183 link:RelNotes/1.8.0.1.txt[1.8.0.1],
184 link:RelNotes/1.8.0.txt[1.8.0].
186 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
189 link:RelNotes/1.7.12.4.txt[1.7.12.4],
190 link:RelNotes/1.7.12.3.txt[1.7.12.3],
191 link:RelNotes/1.7.12.2.txt[1.7.12.2],
192 link:RelNotes/1.7.12.1.txt[1.7.12.1],
193 link:RelNotes/1.7.12.txt[1.7.12].
195 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
198 link:RelNotes/1.7.11.7.txt[1.7.11.7],
199 link:RelNotes/1.7.11.6.txt[1.7.11.6],
200 link:RelNotes/1.7.11.5.txt[1.7.11.5],
201 link:RelNotes/1.7.11.4.txt[1.7.11.4],
202 link:RelNotes/1.7.11.3.txt[1.7.11.3],
203 link:RelNotes/1.7.11.2.txt[1.7.11.2],
204 link:RelNotes/1.7.11.1.txt[1.7.11.1],
205 link:RelNotes/1.7.11.txt[1.7.11].
207 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
210 link:RelNotes/1.7.10.5.txt[1.7.10.5],
211 link:RelNotes/1.7.10.4.txt[1.7.10.4],
212 link:RelNotes/1.7.10.3.txt[1.7.10.3],
213 link:RelNotes/1.7.10.2.txt[1.7.10.2],
214 link:RelNotes/1.7.10.1.txt[1.7.10.1],
215 link:RelNotes/1.7.10.txt[1.7.10].
217 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
220 link:RelNotes/1.7.9.7.txt[1.7.9.7],
221 link:RelNotes/1.7.9.6.txt[1.7.9.6],
222 link:RelNotes/1.7.9.5.txt[1.7.9.5],
223 link:RelNotes/1.7.9.4.txt[1.7.9.4],
224 link:RelNotes/1.7.9.3.txt[1.7.9.3],
225 link:RelNotes/1.7.9.2.txt[1.7.9.2],
226 link:RelNotes/1.7.9.1.txt[1.7.9.1],
227 link:RelNotes/1.7.9.txt[1.7.9].
229 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
232 link:RelNotes/1.7.8.6.txt[1.7.8.6],
233 link:RelNotes/1.7.8.5.txt[1.7.8.5],
234 link:RelNotes/1.7.8.4.txt[1.7.8.4],
235 link:RelNotes/1.7.8.3.txt[1.7.8.3],
236 link:RelNotes/1.7.8.2.txt[1.7.8.2],
237 link:RelNotes/1.7.8.1.txt[1.7.8.1],
238 link:RelNotes/1.7.8.txt[1.7.8].
240 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
243 link:RelNotes/1.7.7.7.txt[1.7.7.7],
244 link:RelNotes/1.7.7.6.txt[1.7.7.6],
245 link:RelNotes/1.7.7.5.txt[1.7.7.5],
246 link:RelNotes/1.7.7.4.txt[1.7.7.4],
247 link:RelNotes/1.7.7.3.txt[1.7.7.3],
248 link:RelNotes/1.7.7.2.txt[1.7.7.2],
249 link:RelNotes/1.7.7.1.txt[1.7.7.1],
250 link:RelNotes/1.7.7.txt[1.7.7].
252 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
255 link:RelNotes/1.7.6.6.txt[1.7.6.6],
256 link:RelNotes/1.7.6.5.txt[1.7.6.5],
257 link:RelNotes/1.7.6.4.txt[1.7.6.4],
258 link:RelNotes/1.7.6.3.txt[1.7.6.3],
259 link:RelNotes/1.7.6.2.txt[1.7.6.2],
260 link:RelNotes/1.7.6.1.txt[1.7.6.1],
261 link:RelNotes/1.7.6.txt[1.7.6].
263 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
266 link:RelNotes/1.7.5.4.txt[1.7.5.4],
267 link:RelNotes/1.7.5.3.txt[1.7.5.3],
268 link:RelNotes/1.7.5.2.txt[1.7.5.2],
269 link:RelNotes/1.7.5.1.txt[1.7.5.1],
270 link:RelNotes/1.7.5.txt[1.7.5].
272 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
275 link:RelNotes/1.7.4.5.txt[1.7.4.5],
276 link:RelNotes/1.7.4.4.txt[1.7.4.4],
277 link:RelNotes/1.7.4.3.txt[1.7.4.3],
278 link:RelNotes/1.7.4.2.txt[1.7.4.2],
279 link:RelNotes/1.7.4.1.txt[1.7.4.1],
280 link:RelNotes/1.7.4.txt[1.7.4].
282 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
285 link:RelNotes/1.7.3.5.txt[1.7.3.5],
286 link:RelNotes/1.7.3.4.txt[1.7.3.4],
287 link:RelNotes/1.7.3.3.txt[1.7.3.3],
288 link:RelNotes/1.7.3.2.txt[1.7.3.2],
289 link:RelNotes/1.7.3.1.txt[1.7.3.1],
290 link:RelNotes/1.7.3.txt[1.7.3].
292 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
295 link:RelNotes/1.7.2.5.txt[1.7.2.5],
296 link:RelNotes/1.7.2.4.txt[1.7.2.4],
297 link:RelNotes/1.7.2.3.txt[1.7.2.3],
298 link:RelNotes/1.7.2.2.txt[1.7.2.2],
299 link:RelNotes/1.7.2.1.txt[1.7.2.1],
300 link:RelNotes/1.7.2.txt[1.7.2].
302 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
305 link:RelNotes/1.7.1.4.txt[1.7.1.4],
306 link:RelNotes/1.7.1.3.txt[1.7.1.3],
307 link:RelNotes/1.7.1.2.txt[1.7.1.2],
308 link:RelNotes/1.7.1.1.txt[1.7.1.1],
309 link:RelNotes/1.7.1.txt[1.7.1].
311 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
314 link:RelNotes/1.7.0.9.txt[1.7.0.9],
315 link:RelNotes/1.7.0.8.txt[1.7.0.8],
316 link:RelNotes/1.7.0.7.txt[1.7.0.7],
317 link:RelNotes/1.7.0.6.txt[1.7.0.6],
318 link:RelNotes/1.7.0.5.txt[1.7.0.5],
319 link:RelNotes/1.7.0.4.txt[1.7.0.4],
320 link:RelNotes/1.7.0.3.txt[1.7.0.3],
321 link:RelNotes/1.7.0.2.txt[1.7.0.2],
322 link:RelNotes/1.7.0.1.txt[1.7.0.1],
323 link:RelNotes/1.7.0.txt[1.7.0].
325 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
328 link:RelNotes/1.6.6.3.txt[1.6.6.3],
329 link:RelNotes/1.6.6.2.txt[1.6.6.2],
330 link:RelNotes/1.6.6.1.txt[1.6.6.1],
331 link:RelNotes/1.6.6.txt[1.6.6].
333 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
336 link:RelNotes/1.6.5.9.txt[1.6.5.9],
337 link:RelNotes/1.6.5.8.txt[1.6.5.8],
338 link:RelNotes/1.6.5.7.txt[1.6.5.7],
339 link:RelNotes/1.6.5.6.txt[1.6.5.6],
340 link:RelNotes/1.6.5.5.txt[1.6.5.5],
341 link:RelNotes/1.6.5.4.txt[1.6.5.4],
342 link:RelNotes/1.6.5.3.txt[1.6.5.3],
343 link:RelNotes/1.6.5.2.txt[1.6.5.2],
344 link:RelNotes/1.6.5.1.txt[1.6.5.1],
345 link:RelNotes/1.6.5.txt[1.6.5].
347 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
350 link:RelNotes/1.6.4.5.txt[1.6.4.5],
351 link:RelNotes/1.6.4.4.txt[1.6.4.4],
352 link:RelNotes/1.6.4.3.txt[1.6.4.3],
353 link:RelNotes/1.6.4.2.txt[1.6.4.2],
354 link:RelNotes/1.6.4.1.txt[1.6.4.1],
355 link:RelNotes/1.6.4.txt[1.6.4].
357 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
360 link:RelNotes/1.6.3.4.txt[1.6.3.4],
361 link:RelNotes/1.6.3.3.txt[1.6.3.3],
362 link:RelNotes/1.6.3.2.txt[1.6.3.2],
363 link:RelNotes/1.6.3.1.txt[1.6.3.1],
364 link:RelNotes/1.6.3.txt[1.6.3].
367 link:RelNotes/1.6.2.5.txt[1.6.2.5],
368 link:RelNotes/1.6.2.4.txt[1.6.2.4],
369 link:RelNotes/1.6.2.3.txt[1.6.2.3],
370 link:RelNotes/1.6.2.2.txt[1.6.2.2],
371 link:RelNotes/1.6.2.1.txt[1.6.2.1],
372 link:RelNotes/1.6.2.txt[1.6.2].
374 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
377 link:RelNotes/1.6.1.3.txt[1.6.1.3],
378 link:RelNotes/1.6.1.2.txt[1.6.1.2],
379 link:RelNotes/1.6.1.1.txt[1.6.1.1],
380 link:RelNotes/1.6.1.txt[1.6.1].
382 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
385 link:RelNotes/1.6.0.6.txt[1.6.0.6],
386 link:RelNotes/1.6.0.5.txt[1.6.0.5],
387 link:RelNotes/1.6.0.4.txt[1.6.0.4],
388 link:RelNotes/1.6.0.3.txt[1.6.0.3],
389 link:RelNotes/1.6.0.2.txt[1.6.0.2],
390 link:RelNotes/1.6.0.1.txt[1.6.0.1],
391 link:RelNotes/1.6.0.txt[1.6.0].
393 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
396 link:RelNotes/1.5.6.6.txt[1.5.6.6],
397 link:RelNotes/1.5.6.5.txt[1.5.6.5],
398 link:RelNotes/1.5.6.4.txt[1.5.6.4],
399 link:RelNotes/1.5.6.3.txt[1.5.6.3],
400 link:RelNotes/1.5.6.2.txt[1.5.6.2],
401 link:RelNotes/1.5.6.1.txt[1.5.6.1],
402 link:RelNotes/1.5.6.txt[1.5.6].
404 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
407 link:RelNotes/1.5.5.6.txt[1.5.5.6],
408 link:RelNotes/1.5.5.5.txt[1.5.5.5],
409 link:RelNotes/1.5.5.4.txt[1.5.5.4],
410 link:RelNotes/1.5.5.3.txt[1.5.5.3],
411 link:RelNotes/1.5.5.2.txt[1.5.5.2],
412 link:RelNotes/1.5.5.1.txt[1.5.5.1],
413 link:RelNotes/1.5.5.txt[1.5.5].
415 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
418 link:RelNotes/1.5.4.7.txt[1.5.4.7],
419 link:RelNotes/1.5.4.6.txt[1.5.4.6],
420 link:RelNotes/1.5.4.5.txt[1.5.4.5],
421 link:RelNotes/1.5.4.4.txt[1.5.4.4],
422 link:RelNotes/1.5.4.3.txt[1.5.4.3],
423 link:RelNotes/1.5.4.2.txt[1.5.4.2],
424 link:RelNotes/1.5.4.1.txt[1.5.4.1],
425 link:RelNotes/1.5.4.txt[1.5.4].
427 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
430 link:RelNotes/1.5.3.8.txt[1.5.3.8],
431 link:RelNotes/1.5.3.7.txt[1.5.3.7],
432 link:RelNotes/1.5.3.6.txt[1.5.3.6],
433 link:RelNotes/1.5.3.5.txt[1.5.3.5],
434 link:RelNotes/1.5.3.4.txt[1.5.3.4],
435 link:RelNotes/1.5.3.3.txt[1.5.3.3],
436 link:RelNotes/1.5.3.2.txt[1.5.3.2],
437 link:RelNotes/1.5.3.1.txt[1.5.3.1],
438 link:RelNotes/1.5.3.txt[1.5.3].
440 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
443 link:RelNotes/1.5.2.5.txt[1.5.2.5],
444 link:RelNotes/1.5.2.4.txt[1.5.2.4],
445 link:RelNotes/1.5.2.3.txt[1.5.2.3],
446 link:RelNotes/1.5.2.2.txt[1.5.2.2],
447 link:RelNotes/1.5.2.1.txt[1.5.2.1],
448 link:RelNotes/1.5.2.txt[1.5.2].
450 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
453 link:RelNotes/1.5.1.6.txt[1.5.1.6],
454 link:RelNotes/1.5.1.5.txt[1.5.1.5],
455 link:RelNotes/1.5.1.4.txt[1.5.1.4],
456 link:RelNotes/1.5.1.3.txt[1.5.1.3],
457 link:RelNotes/1.5.1.2.txt[1.5.1.2],
458 link:RelNotes/1.5.1.1.txt[1.5.1.1],
459 link:RelNotes/1.5.1.txt[1.5.1].
461 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
464 link:RelNotes/1.5.0.7.txt[1.5.0.7],
465 link:RelNotes/1.5.0.6.txt[1.5.0.6],
466 link:RelNotes/1.5.0.5.txt[1.5.0.5],
467 link:RelNotes/1.5.0.3.txt[1.5.0.3],
468 link:RelNotes/1.5.0.2.txt[1.5.0.2],
469 link:RelNotes/1.5.0.1.txt[1.5.0.1],
470 link:RelNotes/1.5.0.txt[1.5.0].
472 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
473 link:v1.3.3/git.html[1.3.3],
474 link:v1.2.6/git.html[1.2.6],
475 link:v1.0.13/git.html[1.0.13].
484 Prints the Git suite version that the 'git' program came from.
487 Prints the synopsis and a list of the most commonly used
488 commands. If the option '--all' or '-a' is given then all
489 available commands are printed. If a Git command is named this
490 option will bring up the manual page for that command.
492 Other options are available to control how the manual page is
493 displayed. See linkgit:git-help[1] for more information,
494 because `git --help ...` is converted internally into `git
498 Run as if git was started in '<path>' instead of the current working
499 directory. When multiple `-C` options are given, each subsequent
500 non-absolute `-C <path>` is interpreted relative to the preceding `-C
503 This option affects options that expect path name like `--git-dir` and
504 `--work-tree` in that their interpretations of the path names would be
505 made relative to the working directory caused by the `-C` option. For
506 example the following invocations are equivalent:
508 git --git-dir=a.git --work-tree=b -C c status
509 git --git-dir=c/a.git --work-tree=c/b status
512 Pass a configuration parameter to the command. The value
513 given will override values from configuration files.
514 The <name> is expected in the same format as listed by
515 'git config' (subkeys separated by dots).
517 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
518 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
519 config file). Including the equals but with an empty value (like `git -c
520 foo.bar= ...`) sets `foo.bar` to the empty string.
522 --exec-path[=<path>]::
523 Path to wherever your core Git programs are installed.
524 This can also be controlled by setting the GIT_EXEC_PATH
525 environment variable. If no path is given, 'git' will print
526 the current setting and then exit.
529 Print the path, without trailing slash, where Git's HTML
530 documentation is installed and exit.
533 Print the manpath (see `man(1)`) for the man pages for
534 this version of Git and exit.
537 Print the path where the Info files documenting this
538 version of Git are installed and exit.
542 Pipe all output into 'less' (or if set, $PAGER) if standard
543 output is a terminal. This overrides the `pager.<cmd>`
544 configuration options (see the "Configuration Mechanism" section
548 Do not pipe Git output into a pager.
551 Set the path to the repository. This can also be controlled by
552 setting the GIT_DIR environment variable. It can be an absolute
553 path or relative path to current working directory.
556 Set the path to the working tree. It can be an absolute path
557 or a path relative to the current working directory.
558 This can also be controlled by setting the GIT_WORK_TREE
559 environment variable and the core.worktree configuration
560 variable (see core.worktree in linkgit:git-config[1] for a
561 more detailed discussion).
564 Set the Git namespace. See linkgit:gitnamespaces[7] for more
565 details. Equivalent to setting the `GIT_NAMESPACE` environment
569 Treat the repository as a bare repository. If GIT_DIR
570 environment is not set, it is set to the current working
573 --no-replace-objects::
574 Do not use replacement refs to replace Git objects. See
575 linkgit:git-replace[1] for more information.
577 --literal-pathspecs::
578 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
579 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
583 Add "glob" magic to all pathspec. This is equivalent to setting
584 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
585 globbing on individual pathspecs can be done using pathspec
589 Add "literal" magic to all pathspec. This is equivalent to setting
590 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
591 globbing on individual pathspecs can be done using pathspec
595 Add "icase" magic to all pathspec. This is equivalent to setting
596 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
601 We divide Git into high level ("porcelain") commands and low level
602 ("plumbing") commands.
604 High-level commands (porcelain)
605 -------------------------------
607 We separate the porcelain commands into the main commands and some
608 ancillary user utilities.
610 Main porcelain commands
611 ~~~~~~~~~~~~~~~~~~~~~~~
613 include::cmds-mainporcelain.txt[]
619 include::cmds-ancillarymanipulators.txt[]
623 include::cmds-ancillaryinterrogators.txt[]
626 Interacting with Others
627 ~~~~~~~~~~~~~~~~~~~~~~~
629 These commands are to interact with foreign SCM and with other
630 people via patch over e-mail.
632 include::cmds-foreignscminterface.txt[]
635 Low-level commands (plumbing)
636 -----------------------------
638 Although Git includes its
639 own porcelain layer, its low-level commands are sufficient to support
640 development of alternative porcelains. Developers of such porcelains
641 might start by reading about linkgit:git-update-index[1] and
642 linkgit:git-read-tree[1].
644 The interface (input, output, set of options and the semantics)
645 to these low-level commands are meant to be a lot more stable
646 than Porcelain level commands, because these commands are
647 primarily for scripted use. The interface to Porcelain commands
648 on the other hand are subject to change in order to improve the
651 The following description divides
652 the low-level commands into commands that manipulate objects (in
653 the repository, index, and working tree), commands that interrogate and
654 compare objects, and commands that move objects and references between
658 Manipulation commands
659 ~~~~~~~~~~~~~~~~~~~~~
661 include::cmds-plumbingmanipulators.txt[]
664 Interrogation commands
665 ~~~~~~~~~~~~~~~~~~~~~~
667 include::cmds-plumbinginterrogators.txt[]
669 In general, the interrogate commands do not touch the files in
673 Synching repositories
674 ~~~~~~~~~~~~~~~~~~~~~
676 include::cmds-synchingrepositories.txt[]
678 The following are helper commands used by the above; end users
679 typically do not use them directly.
681 include::cmds-synchelpers.txt[]
684 Internal helper commands
685 ~~~~~~~~~~~~~~~~~~~~~~~~
687 These are internal helper commands used by other commands; end
688 users typically do not use them directly.
690 include::cmds-purehelpers.txt[]
693 Configuration Mechanism
694 -----------------------
696 Git uses a simple text format to store customizations that are per
697 repository and are per user. Such a configuration file may look
702 # A '#' or ';' character indicates a comment.
707 ; Don't trust file modes
712 name = "Junio C Hamano"
713 email = "gitster@pobox.com"
717 Various commands read from the configuration file and adjust
718 their operation accordingly. See linkgit:git-config[1] for a
719 list and more details about the configuration mechanism.
722 Identifier Terminology
723 ----------------------
725 Indicates the object name for any type of object.
728 Indicates a blob object name.
731 Indicates a tree object name.
734 Indicates a commit object name.
737 Indicates a tree, commit or tag object name. A
738 command that takes a <tree-ish> argument ultimately wants to
739 operate on a <tree> object but automatically dereferences
740 <commit> and <tag> objects that point at a <tree>.
743 Indicates a commit or tag object name. A
744 command that takes a <commit-ish> argument ultimately wants to
745 operate on a <commit> object but automatically dereferences
746 <tag> objects that point at a <commit>.
749 Indicates that an object type is required.
750 Currently one of: `blob`, `tree`, `commit`, or `tag`.
753 Indicates a filename - almost always relative to the
754 root of the tree structure `GIT_INDEX_FILE` describes.
758 Any Git command accepting any <object> can also use the following
762 indicates the head of the current branch.
766 (i.e. a `refs/tags/<tag>` reference).
770 (i.e. a `refs/heads/<head>` reference).
772 For a more complete list of ways to spell object names, see
773 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
776 File/Directory Structure
777 ------------------------
779 Please see the linkgit:gitrepository-layout[5] document.
781 Read linkgit:githooks[5] for more details about each hook.
783 Higher level SCMs may provide and manage additional information in the
789 Please see linkgit:gitglossary[7].
792 Environment Variables
793 ---------------------
794 Various Git commands use the following environment variables:
798 These environment variables apply to 'all' core Git commands. Nb: it
799 is worth noting that they may be used/overridden by SCMS sitting above
800 Git so take care if using a foreign front-end.
803 This environment allows the specification of an alternate
804 index file. If not specified, the default of `$GIT_DIR/index`
807 'GIT_INDEX_VERSION'::
808 This environment variable allows the specification of an index
809 version for new repositories. It won't affect existing index
810 files. By default index file version 2 or 3 is used. See
811 linkgit:git-update-index[1] for more information.
813 'GIT_OBJECT_DIRECTORY'::
814 If the object storage directory is specified via this
815 environment variable then the sha1 directories are created
816 underneath - otherwise the default `$GIT_DIR/objects`
819 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
820 Due to the immutable nature of Git objects, old objects can be
821 archived into shared, read-only directories. This variable
822 specifies a ":" separated (on Windows ";" separated) list
823 of Git object directories which can be used to search for Git
824 objects. New objects will not be written to these directories.
827 If the 'GIT_DIR' environment variable is set then it
828 specifies a path to use instead of the default `.git`
829 for the base of the repository.
830 The '--git-dir' command-line option also sets this value.
833 Set the path to the root of the working tree.
834 This can also be controlled by the '--work-tree' command-line
835 option and the core.worktree configuration variable.
838 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
839 The '--namespace' command-line option also sets this value.
841 'GIT_CEILING_DIRECTORIES'::
842 This should be a colon-separated list of absolute paths. If
843 set, it is a list of directories that Git should not chdir up
844 into while looking for a repository directory (useful for
845 excluding slow-loading network directories). It will not
846 exclude the current working directory or a GIT_DIR set on the
847 command line or in the environment. Normally, Git has to read
848 the entries in this list and resolve any symlink that
849 might be present in order to compare them with the current
850 directory. However, if even this access is slow, you
851 can add an empty entry to the list to tell Git that the
852 subsequent entries are not symlinks and needn't be resolved;
854 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
856 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
857 When run in a directory that does not have ".git" repository
858 directory, Git tries to find such a directory in the parent
859 directories to find the top of the working tree, but by default it
860 does not cross filesystem boundaries. This environment variable
861 can be set to true to tell Git not to stop at filesystem
862 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
863 an explicit repository directory set via 'GIT_DIR' or on the
867 If this variable is set to a path, non-worktree files that are
868 normally in $GIT_DIR will be taken from this path
869 instead. Worktree-specific files such as HEAD or index are
870 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
871 linkgit:git-worktree[1] for
872 details. This variable has lower precedence than other path
873 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
880 'GIT_COMMITTER_NAME'::
881 'GIT_COMMITTER_EMAIL'::
882 'GIT_COMMITTER_DATE'::
884 see linkgit:git-commit-tree[1]
889 Only valid setting is "--unified=??" or "-u??" to set the
890 number of context lines shown when a unified diff is created.
891 This takes precedence over any "-U" or "--unified" option
892 value passed on the Git diff command line.
894 'GIT_EXTERNAL_DIFF'::
895 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
896 program named by it is called, instead of the diff invocation
897 described above. For a path that is added, removed, or modified,
898 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
900 path old-file old-hex old-mode new-file new-hex new-mode
904 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
905 contents of <old|new>,
906 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
907 <old|new>-mode:: are the octal representation of the file modes.
909 The file parameters can point at the user's working file
910 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
911 when a new file is added), or a temporary file (e.g. `old-file` in the
912 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
913 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
915 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
918 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
919 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
921 'GIT_DIFF_PATH_COUNTER'::
922 A 1-based counter incremented by one for every path.
924 'GIT_DIFF_PATH_TOTAL'::
925 The total number of paths.
929 'GIT_MERGE_VERBOSITY'::
930 A number controlling the amount of output shown by
931 the recursive merge strategy. Overrides merge.verbosity.
932 See linkgit:git-merge[1]
935 This environment variable overrides `$PAGER`. If it is set
936 to an empty string or to the value "cat", Git will not launch
937 a pager. See also the `core.pager` option in
938 linkgit:git-config[1].
941 This environment variable overrides `$EDITOR` and `$VISUAL`.
942 It is used by several Git commands when, on interactive mode,
943 an editor is to be launched. See also linkgit:git-var[1]
944 and the `core.editor` option in linkgit:git-config[1].
948 If either of these environment variables is set then 'git fetch'
949 and 'git push' will use the specified command instead of 'ssh'
950 when they need to connect to a remote system.
951 The command will be given exactly two or four arguments: the
952 'username@host' (or just 'host') from the URL and the shell
953 command to execute on that remote system, optionally preceded by
954 '-p' (literally) and the 'port' from the URL when it specifies
955 something other than the default SSH port.
957 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
958 by the shell, which allows additional arguments to be included.
959 `$GIT_SSH` on the other hand must be just the path to a program
960 (which can be a wrapper shell script, if additional arguments are
963 Usually it is easier to configure any desired options through your
964 personal `.ssh/config` file. Please consult your ssh documentation
968 If this environment variable is set, then Git commands which need to
969 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
970 will call this program with a suitable prompt as command-line argument
971 and read the password from its STDOUT. See also the 'core.askPass'
972 option in linkgit:git-config[1].
974 'GIT_TERMINAL_PROMPT'::
975 If this environment variable is set to `0`, git will not prompt
976 on the terminal (e.g., when asking for HTTP authentication).
978 'GIT_CONFIG_NOSYSTEM'::
979 Whether to skip reading settings from the system-wide
980 `$(prefix)/etc/gitconfig` file. This environment variable can
981 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
982 predictable environment for a picky script, or you can set it
983 temporarily to avoid using a buggy `/etc/gitconfig` file while
984 waiting for someone with sufficient permissions to fix it.
987 If this environment variable is set to "1", then commands such
988 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
989 'git check-attr' and 'git check-ignore' will
990 force a flush of the output stream after each record have been
992 variable is set to "0", the output of these commands will be done
993 using completely buffered I/O. If this environment variable is
994 not set, Git will choose buffered or record-oriented flushing
995 based on whether stdout appears to be redirected to a file or not.
998 Enables general trace messages, e.g. alias expansion, built-in
999 command execution and external command execution.
1001 If this variable is set to "1", "2" or "true" (comparison
1002 is case insensitive), trace messages will be printed to
1005 If the variable is set to an integer value greater than 2
1006 and lower than 10 (strictly) then Git will interpret this
1007 value as an open file descriptor and will try to write the
1008 trace messages into this file descriptor.
1010 Alternatively, if the variable is set to an absolute path
1011 (starting with a '/' character), Git will interpret this
1012 as a file path and will try to write the trace messages
1015 Unsetting the variable, or setting it to empty, "0" or
1016 "false" (case insensitive) disables trace messages.
1018 'GIT_TRACE_PACK_ACCESS'::
1019 Enables trace messages for all accesses to any packs. For each
1020 access, the pack file name and an offset in the pack is
1021 recorded. This may be helpful for troubleshooting some
1022 pack-related performance problems.
1023 See 'GIT_TRACE' for available trace output options.
1025 'GIT_TRACE_PACKET'::
1026 Enables trace messages for all packets coming in or out of a
1027 given program. This can help with debugging object negotiation
1028 or other protocol issues. Tracing is turned off at a packet
1029 starting with "PACK" (but see 'GIT_TRACE_PACKFILE' below).
1030 See 'GIT_TRACE' for available trace output options.
1032 'GIT_TRACE_PACKFILE'::
1033 Enables tracing of packfiles sent or received by a
1034 given program. Unlike other trace output, this trace is
1035 verbatim: no headers, and no quoting of binary data. You almost
1036 certainly want to direct into a file (e.g.,
1037 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1038 the terminal or mixing it with other trace output.
1040 Note that this is currently only implemented for the client side
1041 of clones and fetches.
1043 'GIT_TRACE_PERFORMANCE'::
1044 Enables performance related trace messages, e.g. total execution
1045 time of each Git command.
1046 See 'GIT_TRACE' for available trace output options.
1049 Enables trace messages printing the .git, working tree and current
1050 working directory after Git has completed its setup phase.
1051 See 'GIT_TRACE' for available trace output options.
1053 'GIT_TRACE_SHALLOW'::
1054 Enables trace messages that can help debugging fetching /
1055 cloning of shallow repositories.
1056 See 'GIT_TRACE' for available trace output options.
1058 GIT_LITERAL_PATHSPECS::
1059 Setting this variable to `1` will cause Git to treat all
1060 pathspecs literally, rather than as glob patterns. For example,
1061 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1062 for commits that touch the path `*.c`, not any paths that the
1063 glob `*.c` matches. You might want this if you are feeding
1064 literal paths to Git (e.g., paths previously given to you by
1065 `git ls-tree`, `--raw` diff output, etc).
1067 GIT_GLOB_PATHSPECS::
1068 Setting this variable to `1` will cause Git to treat all
1069 pathspecs as glob patterns (aka "glob" magic).
1071 GIT_NOGLOB_PATHSPECS::
1072 Setting this variable to `1` will cause Git to treat all
1073 pathspecs as literal (aka "literal" magic).
1075 GIT_ICASE_PATHSPECS::
1076 Setting this variable to `1` will cause Git to treat all
1077 pathspecs as case-insensitive.
1079 'GIT_REFLOG_ACTION'::
1080 When a ref is updated, reflog entries are created to keep
1081 track of the reason why the ref was updated (which is
1082 typically the name of the high-level command that updated
1083 the ref), in addition to the old and new values of the ref.
1084 A scripted Porcelain command can use set_reflog_action
1085 helper function in `git-sh-setup` to set its name to this
1086 variable when it is invoked as the top level command by the
1087 end user, to be recorded in the body of the reflog.
1089 `GIT_REF_PARANOIA`::
1090 If set to `1`, include broken or badly named refs when iterating
1091 over lists of refs. In a normal, non-corrupted repository, this
1092 does nothing. However, enabling it may help git to detect and
1093 abort some operations in the presence of broken refs. Git sets
1094 this variable automatically when performing destructive
1095 operations like linkgit:git-prune[1]. You should not need to set
1096 it yourself unless you want to be paranoid about making sure
1097 an operation has touched every ref (e.g., because you are
1098 cloning a repository to make a backup).
1100 `GIT_ALLOW_PROTOCOL`::
1101 If set, provide a colon-separated list of protocols which are
1102 allowed to be used with fetch/push/clone. This is useful to
1103 restrict recursive submodule initialization from an untrusted
1104 repository. Any protocol not mentioned will be disallowed (i.e.,
1105 this is a whitelist, not a blacklist). If the variable is not
1106 set at all, all protocols are enabled. The protocol names
1107 currently used by git are:
1109 - `file`: any local file-based path (including `file://` URLs,
1112 - `git`: the anonymous git protocol over a direct TCP
1113 connection (or proxy, if configured)
1115 - `ssh`: git over ssh (including `host:path` syntax,
1118 - `rsync`: git over rsync
1120 - `http`: git over http, both "smart http" and "dumb http".
1121 Note that this does _not_ include `https`; if you want both,
1122 you should specify both as `http:https`.
1124 - any external helpers are named by their protocol (e.g., use
1125 `hg` to allow the `git-remote-hg` helper)
1128 Discussion[[Discussion]]
1129 ------------------------
1131 More detail on the following is available from the
1132 link:user-manual.html#git-concepts[Git concepts chapter of the
1133 user-manual] and linkgit:gitcore-tutorial[7].
1135 A Git project normally consists of a working directory with a ".git"
1136 subdirectory at the top level. The .git directory contains, among other
1137 things, a compressed object database representing the complete history
1138 of the project, an "index" file which links that history to the current
1139 contents of the working tree, and named pointers into that history such
1140 as tags and branch heads.
1142 The object database contains objects of three main types: blobs, which
1143 hold file data; trees, which point to blobs and other trees to build up
1144 directory hierarchies; and commits, which each reference a single tree
1145 and some number of parent commits.
1147 The commit, equivalent to what other systems call a "changeset" or
1148 "version", represents a step in the project's history, and each parent
1149 represents an immediately preceding step. Commits with more than one
1150 parent represent merges of independent lines of development.
1152 All objects are named by the SHA-1 hash of their contents, normally
1153 written as a string of 40 hex digits. Such names are globally unique.
1154 The entire history leading up to a commit can be vouched for by signing
1155 just that commit. A fourth object type, the tag, is provided for this
1158 When first created, objects are stored in individual files, but for
1159 efficiency may later be compressed together into "pack files".
1161 Named pointers called refs mark interesting points in history. A ref
1162 may contain the SHA-1 name of an object or the name of another ref. Refs
1163 with names beginning `ref/head/` contain the SHA-1 name of the most
1164 recent commit (or "head") of a branch under development. SHA-1 names of
1165 tags of interest are stored under `ref/tags/`. A special ref named
1166 `HEAD` contains the name of the currently checked-out branch.
1168 The index file is initialized with a list of all paths and, for each
1169 path, a blob object and a set of attributes. The blob object represents
1170 the contents of the file as of the head of the current branch. The
1171 attributes (last modified time, size, etc.) are taken from the
1172 corresponding file in the working tree. Subsequent changes to the
1173 working tree can be found by comparing these attributes. The index may
1174 be updated with new content, and new commits may be created from the
1175 content stored in the index.
1177 The index is also capable of storing multiple entries (called "stages")
1178 for a given pathname. These stages are used to hold the various
1179 unmerged version of a file when a merge is in progress.
1181 FURTHER DOCUMENTATION
1182 ---------------------
1184 See the references in the "description" section to get started
1185 using Git. The following is probably more detail than necessary
1186 for a first-time user.
1188 The link:user-manual.html#git-concepts[Git concepts chapter of the
1189 user-manual] and linkgit:gitcore-tutorial[7] both provide
1190 introductions to the underlying Git architecture.
1192 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1194 See also the link:howto-index.html[howto] documents for some useful
1197 The internals are documented in the
1198 link:technical/api-index.html[Git API documentation].
1200 Users migrating from CVS may also want to
1201 read linkgit:gitcvs-migration[7].
1206 Git was started by Linus Torvalds, and is currently maintained by Junio
1207 C Hamano. Numerous contributions have come from the Git mailing list
1208 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1209 gives you a more complete list of contributors.
1211 If you have a clone of git.git itself, the
1212 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1213 the authors for specific parts of the project.
1218 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1219 development and maintenance is primarily done. You do not have to be
1220 subscribed to the list to send a message there.
1224 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1225 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1226 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1227 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1228 linkgit:gitworkflows[7]
1232 Part of the linkgit:git[1] suite