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.5.4/git.html[documentation for release 2.5.4]
49 link:RelNotes/2.5.4.txt[2.5.4],
50 link:RelNotes/2.5.3.txt[2.5.3],
51 link:RelNotes/2.5.2.txt[2.5.2],
52 link:RelNotes/2.5.1.txt[2.5.1],
53 link:RelNotes/2.5.0.txt[2.5].
55 * link:v2.4.10/git.html[documentation for release 2.4.10]
58 link:RelNotes/2.4.10.txt[2.4.10],
59 link:RelNotes/2.4.9.txt[2.4.9],
60 link:RelNotes/2.4.8.txt[2.4.8],
61 link:RelNotes/2.4.7.txt[2.4.7],
62 link:RelNotes/2.4.6.txt[2.4.6],
63 link:RelNotes/2.4.5.txt[2.4.5],
64 link:RelNotes/2.4.4.txt[2.4.4],
65 link:RelNotes/2.4.3.txt[2.4.3],
66 link:RelNotes/2.4.2.txt[2.4.2],
67 link:RelNotes/2.4.1.txt[2.4.1],
68 link:RelNotes/2.4.0.txt[2.4].
70 * link:v2.3.10/git.html[documentation for release 2.3.10]
73 link:RelNotes/2.3.10.txt[2.3.10],
74 link:RelNotes/2.3.9.txt[2.3.9],
75 link:RelNotes/2.3.8.txt[2.3.8],
76 link:RelNotes/2.3.7.txt[2.3.7],
77 link:RelNotes/2.3.6.txt[2.3.6],
78 link:RelNotes/2.3.5.txt[2.3.5],
79 link:RelNotes/2.3.4.txt[2.3.4],
80 link:RelNotes/2.3.3.txt[2.3.3],
81 link:RelNotes/2.3.2.txt[2.3.2],
82 link:RelNotes/2.3.1.txt[2.3.1],
83 link:RelNotes/2.3.0.txt[2.3].
85 * link:v2.2.3/git.html[documentation for release 2.2.3]
88 link:RelNotes/2.2.3.txt[2.2.3],
89 link:RelNotes/2.2.2.txt[2.2.2],
90 link:RelNotes/2.2.1.txt[2.2.1],
91 link:RelNotes/2.2.0.txt[2.2].
93 * link:v2.1.4/git.html[documentation for release 2.1.4]
96 link:RelNotes/2.1.4.txt[2.1.4],
97 link:RelNotes/2.1.3.txt[2.1.3],
98 link:RelNotes/2.1.2.txt[2.1.2],
99 link:RelNotes/2.1.1.txt[2.1.1],
100 link:RelNotes/2.1.0.txt[2.1].
102 * link:v2.0.5/git.html[documentation for release 2.0.5]
105 link:RelNotes/2.0.5.txt[2.0.5],
106 link:RelNotes/2.0.4.txt[2.0.4],
107 link:RelNotes/2.0.3.txt[2.0.3],
108 link:RelNotes/2.0.2.txt[2.0.2],
109 link:RelNotes/2.0.1.txt[2.0.1],
110 link:RelNotes/2.0.0.txt[2.0.0].
112 * link:v1.9.5/git.html[documentation for release 1.9.5]
115 link:RelNotes/1.9.5.txt[1.9.5],
116 link:RelNotes/1.9.4.txt[1.9.4],
117 link:RelNotes/1.9.3.txt[1.9.3],
118 link:RelNotes/1.9.2.txt[1.9.2],
119 link:RelNotes/1.9.1.txt[1.9.1],
120 link:RelNotes/1.9.0.txt[1.9.0].
122 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
125 link:RelNotes/1.8.5.6.txt[1.8.5.6],
126 link:RelNotes/1.8.5.5.txt[1.8.5.5],
127 link:RelNotes/1.8.5.4.txt[1.8.5.4],
128 link:RelNotes/1.8.5.3.txt[1.8.5.3],
129 link:RelNotes/1.8.5.2.txt[1.8.5.2],
130 link:RelNotes/1.8.5.1.txt[1.8.5.1],
131 link:RelNotes/1.8.5.txt[1.8.5].
133 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
136 link:RelNotes/1.8.4.5.txt[1.8.4.5],
137 link:RelNotes/1.8.4.4.txt[1.8.4.4],
138 link:RelNotes/1.8.4.3.txt[1.8.4.3],
139 link:RelNotes/1.8.4.2.txt[1.8.4.2],
140 link:RelNotes/1.8.4.1.txt[1.8.4.1],
141 link:RelNotes/1.8.4.txt[1.8.4].
143 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
146 link:RelNotes/1.8.3.4.txt[1.8.3.4],
147 link:RelNotes/1.8.3.3.txt[1.8.3.3],
148 link:RelNotes/1.8.3.2.txt[1.8.3.2],
149 link:RelNotes/1.8.3.1.txt[1.8.3.1],
150 link:RelNotes/1.8.3.txt[1.8.3].
152 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
155 link:RelNotes/1.8.2.3.txt[1.8.2.3],
156 link:RelNotes/1.8.2.2.txt[1.8.2.2],
157 link:RelNotes/1.8.2.1.txt[1.8.2.1],
158 link:RelNotes/1.8.2.txt[1.8.2].
160 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
163 link:RelNotes/1.8.1.6.txt[1.8.1.6],
164 link:RelNotes/1.8.1.5.txt[1.8.1.5],
165 link:RelNotes/1.8.1.4.txt[1.8.1.4],
166 link:RelNotes/1.8.1.3.txt[1.8.1.3],
167 link:RelNotes/1.8.1.2.txt[1.8.1.2],
168 link:RelNotes/1.8.1.1.txt[1.8.1.1],
169 link:RelNotes/1.8.1.txt[1.8.1].
171 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
174 link:RelNotes/1.8.0.3.txt[1.8.0.3],
175 link:RelNotes/1.8.0.2.txt[1.8.0.2],
176 link:RelNotes/1.8.0.1.txt[1.8.0.1],
177 link:RelNotes/1.8.0.txt[1.8.0].
179 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
182 link:RelNotes/1.7.12.4.txt[1.7.12.4],
183 link:RelNotes/1.7.12.3.txt[1.7.12.3],
184 link:RelNotes/1.7.12.2.txt[1.7.12.2],
185 link:RelNotes/1.7.12.1.txt[1.7.12.1],
186 link:RelNotes/1.7.12.txt[1.7.12].
188 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
191 link:RelNotes/1.7.11.7.txt[1.7.11.7],
192 link:RelNotes/1.7.11.6.txt[1.7.11.6],
193 link:RelNotes/1.7.11.5.txt[1.7.11.5],
194 link:RelNotes/1.7.11.4.txt[1.7.11.4],
195 link:RelNotes/1.7.11.3.txt[1.7.11.3],
196 link:RelNotes/1.7.11.2.txt[1.7.11.2],
197 link:RelNotes/1.7.11.1.txt[1.7.11.1],
198 link:RelNotes/1.7.11.txt[1.7.11].
200 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
203 link:RelNotes/1.7.10.5.txt[1.7.10.5],
204 link:RelNotes/1.7.10.4.txt[1.7.10.4],
205 link:RelNotes/1.7.10.3.txt[1.7.10.3],
206 link:RelNotes/1.7.10.2.txt[1.7.10.2],
207 link:RelNotes/1.7.10.1.txt[1.7.10.1],
208 link:RelNotes/1.7.10.txt[1.7.10].
210 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
213 link:RelNotes/1.7.9.7.txt[1.7.9.7],
214 link:RelNotes/1.7.9.6.txt[1.7.9.6],
215 link:RelNotes/1.7.9.5.txt[1.7.9.5],
216 link:RelNotes/1.7.9.4.txt[1.7.9.4],
217 link:RelNotes/1.7.9.3.txt[1.7.9.3],
218 link:RelNotes/1.7.9.2.txt[1.7.9.2],
219 link:RelNotes/1.7.9.1.txt[1.7.9.1],
220 link:RelNotes/1.7.9.txt[1.7.9].
222 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
225 link:RelNotes/1.7.8.6.txt[1.7.8.6],
226 link:RelNotes/1.7.8.5.txt[1.7.8.5],
227 link:RelNotes/1.7.8.4.txt[1.7.8.4],
228 link:RelNotes/1.7.8.3.txt[1.7.8.3],
229 link:RelNotes/1.7.8.2.txt[1.7.8.2],
230 link:RelNotes/1.7.8.1.txt[1.7.8.1],
231 link:RelNotes/1.7.8.txt[1.7.8].
233 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
236 link:RelNotes/1.7.7.7.txt[1.7.7.7],
237 link:RelNotes/1.7.7.6.txt[1.7.7.6],
238 link:RelNotes/1.7.7.5.txt[1.7.7.5],
239 link:RelNotes/1.7.7.4.txt[1.7.7.4],
240 link:RelNotes/1.7.7.3.txt[1.7.7.3],
241 link:RelNotes/1.7.7.2.txt[1.7.7.2],
242 link:RelNotes/1.7.7.1.txt[1.7.7.1],
243 link:RelNotes/1.7.7.txt[1.7.7].
245 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
248 link:RelNotes/1.7.6.6.txt[1.7.6.6],
249 link:RelNotes/1.7.6.5.txt[1.7.6.5],
250 link:RelNotes/1.7.6.4.txt[1.7.6.4],
251 link:RelNotes/1.7.6.3.txt[1.7.6.3],
252 link:RelNotes/1.7.6.2.txt[1.7.6.2],
253 link:RelNotes/1.7.6.1.txt[1.7.6.1],
254 link:RelNotes/1.7.6.txt[1.7.6].
256 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
259 link:RelNotes/1.7.5.4.txt[1.7.5.4],
260 link:RelNotes/1.7.5.3.txt[1.7.5.3],
261 link:RelNotes/1.7.5.2.txt[1.7.5.2],
262 link:RelNotes/1.7.5.1.txt[1.7.5.1],
263 link:RelNotes/1.7.5.txt[1.7.5].
265 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
268 link:RelNotes/1.7.4.5.txt[1.7.4.5],
269 link:RelNotes/1.7.4.4.txt[1.7.4.4],
270 link:RelNotes/1.7.4.3.txt[1.7.4.3],
271 link:RelNotes/1.7.4.2.txt[1.7.4.2],
272 link:RelNotes/1.7.4.1.txt[1.7.4.1],
273 link:RelNotes/1.7.4.txt[1.7.4].
275 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
278 link:RelNotes/1.7.3.5.txt[1.7.3.5],
279 link:RelNotes/1.7.3.4.txt[1.7.3.4],
280 link:RelNotes/1.7.3.3.txt[1.7.3.3],
281 link:RelNotes/1.7.3.2.txt[1.7.3.2],
282 link:RelNotes/1.7.3.1.txt[1.7.3.1],
283 link:RelNotes/1.7.3.txt[1.7.3].
285 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
288 link:RelNotes/1.7.2.5.txt[1.7.2.5],
289 link:RelNotes/1.7.2.4.txt[1.7.2.4],
290 link:RelNotes/1.7.2.3.txt[1.7.2.3],
291 link:RelNotes/1.7.2.2.txt[1.7.2.2],
292 link:RelNotes/1.7.2.1.txt[1.7.2.1],
293 link:RelNotes/1.7.2.txt[1.7.2].
295 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
298 link:RelNotes/1.7.1.4.txt[1.7.1.4],
299 link:RelNotes/1.7.1.3.txt[1.7.1.3],
300 link:RelNotes/1.7.1.2.txt[1.7.1.2],
301 link:RelNotes/1.7.1.1.txt[1.7.1.1],
302 link:RelNotes/1.7.1.txt[1.7.1].
304 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
307 link:RelNotes/1.7.0.9.txt[1.7.0.9],
308 link:RelNotes/1.7.0.8.txt[1.7.0.8],
309 link:RelNotes/1.7.0.7.txt[1.7.0.7],
310 link:RelNotes/1.7.0.6.txt[1.7.0.6],
311 link:RelNotes/1.7.0.5.txt[1.7.0.5],
312 link:RelNotes/1.7.0.4.txt[1.7.0.4],
313 link:RelNotes/1.7.0.3.txt[1.7.0.3],
314 link:RelNotes/1.7.0.2.txt[1.7.0.2],
315 link:RelNotes/1.7.0.1.txt[1.7.0.1],
316 link:RelNotes/1.7.0.txt[1.7.0].
318 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
321 link:RelNotes/1.6.6.3.txt[1.6.6.3],
322 link:RelNotes/1.6.6.2.txt[1.6.6.2],
323 link:RelNotes/1.6.6.1.txt[1.6.6.1],
324 link:RelNotes/1.6.6.txt[1.6.6].
326 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
329 link:RelNotes/1.6.5.9.txt[1.6.5.9],
330 link:RelNotes/1.6.5.8.txt[1.6.5.8],
331 link:RelNotes/1.6.5.7.txt[1.6.5.7],
332 link:RelNotes/1.6.5.6.txt[1.6.5.6],
333 link:RelNotes/1.6.5.5.txt[1.6.5.5],
334 link:RelNotes/1.6.5.4.txt[1.6.5.4],
335 link:RelNotes/1.6.5.3.txt[1.6.5.3],
336 link:RelNotes/1.6.5.2.txt[1.6.5.2],
337 link:RelNotes/1.6.5.1.txt[1.6.5.1],
338 link:RelNotes/1.6.5.txt[1.6.5].
340 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
343 link:RelNotes/1.6.4.5.txt[1.6.4.5],
344 link:RelNotes/1.6.4.4.txt[1.6.4.4],
345 link:RelNotes/1.6.4.3.txt[1.6.4.3],
346 link:RelNotes/1.6.4.2.txt[1.6.4.2],
347 link:RelNotes/1.6.4.1.txt[1.6.4.1],
348 link:RelNotes/1.6.4.txt[1.6.4].
350 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
353 link:RelNotes/1.6.3.4.txt[1.6.3.4],
354 link:RelNotes/1.6.3.3.txt[1.6.3.3],
355 link:RelNotes/1.6.3.2.txt[1.6.3.2],
356 link:RelNotes/1.6.3.1.txt[1.6.3.1],
357 link:RelNotes/1.6.3.txt[1.6.3].
360 link:RelNotes/1.6.2.5.txt[1.6.2.5],
361 link:RelNotes/1.6.2.4.txt[1.6.2.4],
362 link:RelNotes/1.6.2.3.txt[1.6.2.3],
363 link:RelNotes/1.6.2.2.txt[1.6.2.2],
364 link:RelNotes/1.6.2.1.txt[1.6.2.1],
365 link:RelNotes/1.6.2.txt[1.6.2].
367 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
370 link:RelNotes/1.6.1.3.txt[1.6.1.3],
371 link:RelNotes/1.6.1.2.txt[1.6.1.2],
372 link:RelNotes/1.6.1.1.txt[1.6.1.1],
373 link:RelNotes/1.6.1.txt[1.6.1].
375 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
378 link:RelNotes/1.6.0.6.txt[1.6.0.6],
379 link:RelNotes/1.6.0.5.txt[1.6.0.5],
380 link:RelNotes/1.6.0.4.txt[1.6.0.4],
381 link:RelNotes/1.6.0.3.txt[1.6.0.3],
382 link:RelNotes/1.6.0.2.txt[1.6.0.2],
383 link:RelNotes/1.6.0.1.txt[1.6.0.1],
384 link:RelNotes/1.6.0.txt[1.6.0].
386 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
389 link:RelNotes/1.5.6.6.txt[1.5.6.6],
390 link:RelNotes/1.5.6.5.txt[1.5.6.5],
391 link:RelNotes/1.5.6.4.txt[1.5.6.4],
392 link:RelNotes/1.5.6.3.txt[1.5.6.3],
393 link:RelNotes/1.5.6.2.txt[1.5.6.2],
394 link:RelNotes/1.5.6.1.txt[1.5.6.1],
395 link:RelNotes/1.5.6.txt[1.5.6].
397 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
400 link:RelNotes/1.5.5.6.txt[1.5.5.6],
401 link:RelNotes/1.5.5.5.txt[1.5.5.5],
402 link:RelNotes/1.5.5.4.txt[1.5.5.4],
403 link:RelNotes/1.5.5.3.txt[1.5.5.3],
404 link:RelNotes/1.5.5.2.txt[1.5.5.2],
405 link:RelNotes/1.5.5.1.txt[1.5.5.1],
406 link:RelNotes/1.5.5.txt[1.5.5].
408 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
411 link:RelNotes/1.5.4.7.txt[1.5.4.7],
412 link:RelNotes/1.5.4.6.txt[1.5.4.6],
413 link:RelNotes/1.5.4.5.txt[1.5.4.5],
414 link:RelNotes/1.5.4.4.txt[1.5.4.4],
415 link:RelNotes/1.5.4.3.txt[1.5.4.3],
416 link:RelNotes/1.5.4.2.txt[1.5.4.2],
417 link:RelNotes/1.5.4.1.txt[1.5.4.1],
418 link:RelNotes/1.5.4.txt[1.5.4].
420 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
423 link:RelNotes/1.5.3.8.txt[1.5.3.8],
424 link:RelNotes/1.5.3.7.txt[1.5.3.7],
425 link:RelNotes/1.5.3.6.txt[1.5.3.6],
426 link:RelNotes/1.5.3.5.txt[1.5.3.5],
427 link:RelNotes/1.5.3.4.txt[1.5.3.4],
428 link:RelNotes/1.5.3.3.txt[1.5.3.3],
429 link:RelNotes/1.5.3.2.txt[1.5.3.2],
430 link:RelNotes/1.5.3.1.txt[1.5.3.1],
431 link:RelNotes/1.5.3.txt[1.5.3].
433 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
436 link:RelNotes/1.5.2.5.txt[1.5.2.5],
437 link:RelNotes/1.5.2.4.txt[1.5.2.4],
438 link:RelNotes/1.5.2.3.txt[1.5.2.3],
439 link:RelNotes/1.5.2.2.txt[1.5.2.2],
440 link:RelNotes/1.5.2.1.txt[1.5.2.1],
441 link:RelNotes/1.5.2.txt[1.5.2].
443 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
446 link:RelNotes/1.5.1.6.txt[1.5.1.6],
447 link:RelNotes/1.5.1.5.txt[1.5.1.5],
448 link:RelNotes/1.5.1.4.txt[1.5.1.4],
449 link:RelNotes/1.5.1.3.txt[1.5.1.3],
450 link:RelNotes/1.5.1.2.txt[1.5.1.2],
451 link:RelNotes/1.5.1.1.txt[1.5.1.1],
452 link:RelNotes/1.5.1.txt[1.5.1].
454 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
457 link:RelNotes/1.5.0.7.txt[1.5.0.7],
458 link:RelNotes/1.5.0.6.txt[1.5.0.6],
459 link:RelNotes/1.5.0.5.txt[1.5.0.5],
460 link:RelNotes/1.5.0.3.txt[1.5.0.3],
461 link:RelNotes/1.5.0.2.txt[1.5.0.2],
462 link:RelNotes/1.5.0.1.txt[1.5.0.1],
463 link:RelNotes/1.5.0.txt[1.5.0].
465 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
466 link:v1.3.3/git.html[1.3.3],
467 link:v1.2.6/git.html[1.2.6],
468 link:v1.0.13/git.html[1.0.13].
477 Prints the Git suite version that the 'git' program came from.
480 Prints the synopsis and a list of the most commonly used
481 commands. If the option '--all' or '-a' is given then all
482 available commands are printed. If a Git command is named this
483 option will bring up the manual page for that command.
485 Other options are available to control how the manual page is
486 displayed. See linkgit:git-help[1] for more information,
487 because `git --help ...` is converted internally into `git
491 Run as if git was started in '<path>' instead of the current working
492 directory. When multiple `-C` options are given, each subsequent
493 non-absolute `-C <path>` is interpreted relative to the preceding `-C
496 This option affects options that expect path name like `--git-dir` and
497 `--work-tree` in that their interpretations of the path names would be
498 made relative to the working directory caused by the `-C` option. For
499 example the following invocations are equivalent:
501 git --git-dir=a.git --work-tree=b -C c status
502 git --git-dir=c/a.git --work-tree=c/b status
505 Pass a configuration parameter to the command. The value
506 given will override values from configuration files.
507 The <name> is expected in the same format as listed by
508 'git config' (subkeys separated by dots).
510 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
511 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
512 config file). Including the equals but with an empty value (like `git -c
513 foo.bar= ...`) sets `foo.bar` to the empty string.
515 --exec-path[=<path>]::
516 Path to wherever your core Git programs are installed.
517 This can also be controlled by setting the GIT_EXEC_PATH
518 environment variable. If no path is given, 'git' will print
519 the current setting and then exit.
522 Print the path, without trailing slash, where Git's HTML
523 documentation is installed and exit.
526 Print the manpath (see `man(1)`) for the man pages for
527 this version of Git and exit.
530 Print the path where the Info files documenting this
531 version of Git are installed and exit.
535 Pipe all output into 'less' (or if set, $PAGER) if standard
536 output is a terminal. This overrides the `pager.<cmd>`
537 configuration options (see the "Configuration Mechanism" section
541 Do not pipe Git output into a pager.
544 Set the path to the repository. This can also be controlled by
545 setting the GIT_DIR environment variable. It can be an absolute
546 path or relative path to current working directory.
549 Set the path to the working tree. It can be an absolute path
550 or a path relative to the current working directory.
551 This can also be controlled by setting the GIT_WORK_TREE
552 environment variable and the core.worktree configuration
553 variable (see core.worktree in linkgit:git-config[1] for a
554 more detailed discussion).
557 Set the Git namespace. See linkgit:gitnamespaces[7] for more
558 details. Equivalent to setting the `GIT_NAMESPACE` environment
562 Treat the repository as a bare repository. If GIT_DIR
563 environment is not set, it is set to the current working
566 --no-replace-objects::
567 Do not use replacement refs to replace Git objects. See
568 linkgit:git-replace[1] for more information.
570 --literal-pathspecs::
571 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
572 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
576 Add "glob" magic to all pathspec. This is equivalent to setting
577 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
578 globbing on individual pathspecs can be done using pathspec
582 Add "literal" magic to all pathspec. This is equivalent to setting
583 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
584 globbing on individual pathspecs can be done using pathspec
588 Add "icase" magic to all pathspec. This is equivalent to setting
589 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
594 We divide Git into high level ("porcelain") commands and low level
595 ("plumbing") commands.
597 High-level commands (porcelain)
598 -------------------------------
600 We separate the porcelain commands into the main commands and some
601 ancillary user utilities.
603 Main porcelain commands
604 ~~~~~~~~~~~~~~~~~~~~~~~
606 include::cmds-mainporcelain.txt[]
612 include::cmds-ancillarymanipulators.txt[]
616 include::cmds-ancillaryinterrogators.txt[]
619 Interacting with Others
620 ~~~~~~~~~~~~~~~~~~~~~~~
622 These commands are to interact with foreign SCM and with other
623 people via patch over e-mail.
625 include::cmds-foreignscminterface.txt[]
628 Low-level commands (plumbing)
629 -----------------------------
631 Although Git includes its
632 own porcelain layer, its low-level commands are sufficient to support
633 development of alternative porcelains. Developers of such porcelains
634 might start by reading about linkgit:git-update-index[1] and
635 linkgit:git-read-tree[1].
637 The interface (input, output, set of options and the semantics)
638 to these low-level commands are meant to be a lot more stable
639 than Porcelain level commands, because these commands are
640 primarily for scripted use. The interface to Porcelain commands
641 on the other hand are subject to change in order to improve the
644 The following description divides
645 the low-level commands into commands that manipulate objects (in
646 the repository, index, and working tree), commands that interrogate and
647 compare objects, and commands that move objects and references between
651 Manipulation commands
652 ~~~~~~~~~~~~~~~~~~~~~
654 include::cmds-plumbingmanipulators.txt[]
657 Interrogation commands
658 ~~~~~~~~~~~~~~~~~~~~~~
660 include::cmds-plumbinginterrogators.txt[]
662 In general, the interrogate commands do not touch the files in
666 Synching repositories
667 ~~~~~~~~~~~~~~~~~~~~~
669 include::cmds-synchingrepositories.txt[]
671 The following are helper commands used by the above; end users
672 typically do not use them directly.
674 include::cmds-synchelpers.txt[]
677 Internal helper commands
678 ~~~~~~~~~~~~~~~~~~~~~~~~
680 These are internal helper commands used by other commands; end
681 users typically do not use them directly.
683 include::cmds-purehelpers.txt[]
686 Configuration Mechanism
687 -----------------------
689 Git uses a simple text format to store customizations that are per
690 repository and are per user. Such a configuration file may look
695 # A '#' or ';' character indicates a comment.
700 ; Don't trust file modes
705 name = "Junio C Hamano"
706 email = "gitster@pobox.com"
710 Various commands read from the configuration file and adjust
711 their operation accordingly. See linkgit:git-config[1] for a
712 list and more details about the configuration mechanism.
715 Identifier Terminology
716 ----------------------
718 Indicates the object name for any type of object.
721 Indicates a blob object name.
724 Indicates a tree object name.
727 Indicates a commit object name.
730 Indicates a tree, commit or tag object name. A
731 command that takes a <tree-ish> argument ultimately wants to
732 operate on a <tree> object but automatically dereferences
733 <commit> and <tag> objects that point at a <tree>.
736 Indicates a commit or tag object name. A
737 command that takes a <commit-ish> argument ultimately wants to
738 operate on a <commit> object but automatically dereferences
739 <tag> objects that point at a <commit>.
742 Indicates that an object type is required.
743 Currently one of: `blob`, `tree`, `commit`, or `tag`.
746 Indicates a filename - almost always relative to the
747 root of the tree structure `GIT_INDEX_FILE` describes.
751 Any Git command accepting any <object> can also use the following
755 indicates the head of the current branch.
759 (i.e. a `refs/tags/<tag>` reference).
763 (i.e. a `refs/heads/<head>` reference).
765 For a more complete list of ways to spell object names, see
766 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
769 File/Directory Structure
770 ------------------------
772 Please see the linkgit:gitrepository-layout[5] document.
774 Read linkgit:githooks[5] for more details about each hook.
776 Higher level SCMs may provide and manage additional information in the
782 Please see linkgit:gitglossary[7].
785 Environment Variables
786 ---------------------
787 Various Git commands use the following environment variables:
791 These environment variables apply to 'all' core Git commands. Nb: it
792 is worth noting that they may be used/overridden by SCMS sitting above
793 Git so take care if using a foreign front-end.
796 This environment allows the specification of an alternate
797 index file. If not specified, the default of `$GIT_DIR/index`
800 'GIT_INDEX_VERSION'::
801 This environment variable allows the specification of an index
802 version for new repositories. It won't affect existing index
803 files. By default index file version 2 or 3 is used. See
804 linkgit:git-update-index[1] for more information.
806 'GIT_OBJECT_DIRECTORY'::
807 If the object storage directory is specified via this
808 environment variable then the sha1 directories are created
809 underneath - otherwise the default `$GIT_DIR/objects`
812 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
813 Due to the immutable nature of Git objects, old objects can be
814 archived into shared, read-only directories. This variable
815 specifies a ":" separated (on Windows ";" separated) list
816 of Git object directories which can be used to search for Git
817 objects. New objects will not be written to these directories.
820 If the 'GIT_DIR' environment variable is set then it
821 specifies a path to use instead of the default `.git`
822 for the base of the repository.
823 The '--git-dir' command-line option also sets this value.
826 Set the path to the root of the working tree.
827 This can also be controlled by the '--work-tree' command-line
828 option and the core.worktree configuration variable.
831 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
832 The '--namespace' command-line option also sets this value.
834 'GIT_CEILING_DIRECTORIES'::
835 This should be a colon-separated list of absolute paths. If
836 set, it is a list of directories that Git should not chdir up
837 into while looking for a repository directory (useful for
838 excluding slow-loading network directories). It will not
839 exclude the current working directory or a GIT_DIR set on the
840 command line or in the environment. Normally, Git has to read
841 the entries in this list and resolve any symlink that
842 might be present in order to compare them with the current
843 directory. However, if even this access is slow, you
844 can add an empty entry to the list to tell Git that the
845 subsequent entries are not symlinks and needn't be resolved;
847 'GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink'.
849 'GIT_DISCOVERY_ACROSS_FILESYSTEM'::
850 When run in a directory that does not have ".git" repository
851 directory, Git tries to find such a directory in the parent
852 directories to find the top of the working tree, but by default it
853 does not cross filesystem boundaries. This environment variable
854 can be set to true to tell Git not to stop at filesystem
855 boundaries. Like 'GIT_CEILING_DIRECTORIES', this will not affect
856 an explicit repository directory set via 'GIT_DIR' or on the
860 If this variable is set to a path, non-worktree files that are
861 normally in $GIT_DIR will be taken from this path
862 instead. Worktree-specific files such as HEAD or index are
863 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
864 linkgit:git-worktree[1] for
865 details. This variable has lower precedence than other path
866 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
873 'GIT_COMMITTER_NAME'::
874 'GIT_COMMITTER_EMAIL'::
875 'GIT_COMMITTER_DATE'::
877 see linkgit:git-commit-tree[1]
882 Only valid setting is "--unified=??" or "-u??" to set the
883 number of context lines shown when a unified diff is created.
884 This takes precedence over any "-U" or "--unified" option
885 value passed on the Git diff command line.
887 'GIT_EXTERNAL_DIFF'::
888 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
889 program named by it is called, instead of the diff invocation
890 described above. For a path that is added, removed, or modified,
891 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
893 path old-file old-hex old-mode new-file new-hex new-mode
897 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
898 contents of <old|new>,
899 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
900 <old|new>-mode:: are the octal representation of the file modes.
902 The file parameters can point at the user's working file
903 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
904 when a new file is added), or a temporary file (e.g. `old-file` in the
905 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
906 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
908 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
911 For each path 'GIT_EXTERNAL_DIFF' is called, two environment variables,
912 'GIT_DIFF_PATH_COUNTER' and 'GIT_DIFF_PATH_TOTAL' are set.
914 'GIT_DIFF_PATH_COUNTER'::
915 A 1-based counter incremented by one for every path.
917 'GIT_DIFF_PATH_TOTAL'::
918 The total number of paths.
922 'GIT_MERGE_VERBOSITY'::
923 A number controlling the amount of output shown by
924 the recursive merge strategy. Overrides merge.verbosity.
925 See linkgit:git-merge[1]
928 This environment variable overrides `$PAGER`. If it is set
929 to an empty string or to the value "cat", Git will not launch
930 a pager. See also the `core.pager` option in
931 linkgit:git-config[1].
934 This environment variable overrides `$EDITOR` and `$VISUAL`.
935 It is used by several Git commands when, on interactive mode,
936 an editor is to be launched. See also linkgit:git-var[1]
937 and the `core.editor` option in linkgit:git-config[1].
941 If either of these environment variables is set then 'git fetch'
942 and 'git push' will use the specified command instead of 'ssh'
943 when they need to connect to a remote system.
944 The command will be given exactly two or four arguments: the
945 'username@host' (or just 'host') from the URL and the shell
946 command to execute on that remote system, optionally preceded by
947 '-p' (literally) and the 'port' from the URL when it specifies
948 something other than the default SSH port.
950 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
951 by the shell, which allows additional arguments to be included.
952 `$GIT_SSH` on the other hand must be just the path to a program
953 (which can be a wrapper shell script, if additional arguments are
956 Usually it is easier to configure any desired options through your
957 personal `.ssh/config` file. Please consult your ssh documentation
961 If this environment variable is set, then Git commands which need to
962 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
963 will call this program with a suitable prompt as command-line argument
964 and read the password from its STDOUT. See also the 'core.askPass'
965 option in linkgit:git-config[1].
967 'GIT_TERMINAL_PROMPT'::
968 If this environment variable is set to `0`, git will not prompt
969 on the terminal (e.g., when asking for HTTP authentication).
971 'GIT_CONFIG_NOSYSTEM'::
972 Whether to skip reading settings from the system-wide
973 `$(prefix)/etc/gitconfig` file. This environment variable can
974 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
975 predictable environment for a picky script, or you can set it
976 temporarily to avoid using a buggy `/etc/gitconfig` file while
977 waiting for someone with sufficient permissions to fix it.
980 If this environment variable is set to "1", then commands such
981 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
982 'git check-attr' and 'git check-ignore' will
983 force a flush of the output stream after each record have been
985 variable is set to "0", the output of these commands will be done
986 using completely buffered I/O. If this environment variable is
987 not set, Git will choose buffered or record-oriented flushing
988 based on whether stdout appears to be redirected to a file or not.
991 Enables general trace messages, e.g. alias expansion, built-in
992 command execution and external command execution.
994 If this variable is set to "1", "2" or "true" (comparison
995 is case insensitive), trace messages will be printed to
998 If the variable is set to an integer value greater than 2
999 and lower than 10 (strictly) then Git will interpret this
1000 value as an open file descriptor and will try to write the
1001 trace messages into this file descriptor.
1003 Alternatively, if the variable is set to an absolute path
1004 (starting with a '/' character), Git will interpret this
1005 as a file path and will try to write the trace messages
1008 Unsetting the variable, or setting it to empty, "0" or
1009 "false" (case insensitive) disables trace messages.
1011 'GIT_TRACE_PACK_ACCESS'::
1012 Enables trace messages for all accesses to any packs. For each
1013 access, the pack file name and an offset in the pack is
1014 recorded. This may be helpful for troubleshooting some
1015 pack-related performance problems.
1016 See 'GIT_TRACE' for available trace output options.
1018 'GIT_TRACE_PACKET'::
1019 Enables trace messages for all packets coming in or out of a
1020 given program. This can help with debugging object negotiation
1021 or other protocol issues. Tracing is turned off at a packet
1022 starting with "PACK".
1023 See 'GIT_TRACE' for available trace output options.
1025 'GIT_TRACE_PERFORMANCE'::
1026 Enables performance related trace messages, e.g. total execution
1027 time of each Git command.
1028 See 'GIT_TRACE' for available trace output options.
1031 Enables trace messages printing the .git, working tree and current
1032 working directory after Git has completed its setup phase.
1033 See 'GIT_TRACE' for available trace output options.
1035 'GIT_TRACE_SHALLOW'::
1036 Enables trace messages that can help debugging fetching /
1037 cloning of shallow repositories.
1038 See 'GIT_TRACE' for available trace output options.
1040 GIT_LITERAL_PATHSPECS::
1041 Setting this variable to `1` will cause Git to treat all
1042 pathspecs literally, rather than as glob patterns. For example,
1043 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1044 for commits that touch the path `*.c`, not any paths that the
1045 glob `*.c` matches. You might want this if you are feeding
1046 literal paths to Git (e.g., paths previously given to you by
1047 `git ls-tree`, `--raw` diff output, etc).
1049 GIT_GLOB_PATHSPECS::
1050 Setting this variable to `1` will cause Git to treat all
1051 pathspecs as glob patterns (aka "glob" magic).
1053 GIT_NOGLOB_PATHSPECS::
1054 Setting this variable to `1` will cause Git to treat all
1055 pathspecs as literal (aka "literal" magic).
1057 GIT_ICASE_PATHSPECS::
1058 Setting this variable to `1` will cause Git to treat all
1059 pathspecs as case-insensitive.
1061 'GIT_REFLOG_ACTION'::
1062 When a ref is updated, reflog entries are created to keep
1063 track of the reason why the ref was updated (which is
1064 typically the name of the high-level command that updated
1065 the ref), in addition to the old and new values of the ref.
1066 A scripted Porcelain command can use set_reflog_action
1067 helper function in `git-sh-setup` to set its name to this
1068 variable when it is invoked as the top level command by the
1069 end user, to be recorded in the body of the reflog.
1071 `GIT_REF_PARANOIA`::
1072 If set to `1`, include broken or badly named refs when iterating
1073 over lists of refs. In a normal, non-corrupted repository, this
1074 does nothing. However, enabling it may help git to detect and
1075 abort some operations in the presence of broken refs. Git sets
1076 this variable automatically when performing destructive
1077 operations like linkgit:git-prune[1]. You should not need to set
1078 it yourself unless you want to be paranoid about making sure
1079 an operation has touched every ref (e.g., because you are
1080 cloning a repository to make a backup).
1082 `GIT_ALLOW_PROTOCOL`::
1083 If set, provide a colon-separated list of protocols which are
1084 allowed to be used with fetch/push/clone. This is useful to
1085 restrict recursive submodule initialization from an untrusted
1086 repository. Any protocol not mentioned will be disallowed (i.e.,
1087 this is a whitelist, not a blacklist). If the variable is not
1088 set at all, all protocols are enabled. The protocol names
1089 currently used by git are:
1091 - `file`: any local file-based path (including `file://` URLs,
1094 - `git`: the anonymous git protocol over a direct TCP
1095 connection (or proxy, if configured)
1097 - `ssh`: git over ssh (including `host:path` syntax,
1100 - `rsync`: git over rsync
1102 - `http`: git over http, both "smart http" and "dumb http".
1103 Note that this does _not_ include `https`; if you want both,
1104 you should specify both as `http:https`.
1106 - any external helpers are named by their protocol (e.g., use
1107 `hg` to allow the `git-remote-hg` helper)
1110 Discussion[[Discussion]]
1111 ------------------------
1113 More detail on the following is available from the
1114 link:user-manual.html#git-concepts[Git concepts chapter of the
1115 user-manual] and linkgit:gitcore-tutorial[7].
1117 A Git project normally consists of a working directory with a ".git"
1118 subdirectory at the top level. The .git directory contains, among other
1119 things, a compressed object database representing the complete history
1120 of the project, an "index" file which links that history to the current
1121 contents of the working tree, and named pointers into that history such
1122 as tags and branch heads.
1124 The object database contains objects of three main types: blobs, which
1125 hold file data; trees, which point to blobs and other trees to build up
1126 directory hierarchies; and commits, which each reference a single tree
1127 and some number of parent commits.
1129 The commit, equivalent to what other systems call a "changeset" or
1130 "version", represents a step in the project's history, and each parent
1131 represents an immediately preceding step. Commits with more than one
1132 parent represent merges of independent lines of development.
1134 All objects are named by the SHA-1 hash of their contents, normally
1135 written as a string of 40 hex digits. Such names are globally unique.
1136 The entire history leading up to a commit can be vouched for by signing
1137 just that commit. A fourth object type, the tag, is provided for this
1140 When first created, objects are stored in individual files, but for
1141 efficiency may later be compressed together into "pack files".
1143 Named pointers called refs mark interesting points in history. A ref
1144 may contain the SHA-1 name of an object or the name of another ref. Refs
1145 with names beginning `ref/head/` contain the SHA-1 name of the most
1146 recent commit (or "head") of a branch under development. SHA-1 names of
1147 tags of interest are stored under `ref/tags/`. A special ref named
1148 `HEAD` contains the name of the currently checked-out branch.
1150 The index file is initialized with a list of all paths and, for each
1151 path, a blob object and a set of attributes. The blob object represents
1152 the contents of the file as of the head of the current branch. The
1153 attributes (last modified time, size, etc.) are taken from the
1154 corresponding file in the working tree. Subsequent changes to the
1155 working tree can be found by comparing these attributes. The index may
1156 be updated with new content, and new commits may be created from the
1157 content stored in the index.
1159 The index is also capable of storing multiple entries (called "stages")
1160 for a given pathname. These stages are used to hold the various
1161 unmerged version of a file when a merge is in progress.
1163 FURTHER DOCUMENTATION
1164 ---------------------
1166 See the references in the "description" section to get started
1167 using Git. The following is probably more detail than necessary
1168 for a first-time user.
1170 The link:user-manual.html#git-concepts[Git concepts chapter of the
1171 user-manual] and linkgit:gitcore-tutorial[7] both provide
1172 introductions to the underlying Git architecture.
1174 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1176 See also the link:howto-index.html[howto] documents for some useful
1179 The internals are documented in the
1180 link:technical/api-index.html[Git API documentation].
1182 Users migrating from CVS may also want to
1183 read linkgit:gitcvs-migration[7].
1188 Git was started by Linus Torvalds, and is currently maintained by Junio
1189 C Hamano. Numerous contributions have come from the Git mailing list
1190 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1191 gives you a more complete list of contributors.
1193 If you have a clone of git.git itself, the
1194 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1195 the authors for specific parts of the project.
1200 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1201 development and maintenance is primarily done. You do not have to be
1202 subscribed to the list to send a message there.
1206 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1207 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1208 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1209 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1210 linkgit:gitworkflows[7]
1214 Part of the linkgit:git[1] suite