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>]
16 [--super-prefix=<path>]
21 Git is a fast, scalable, distributed revision control system with an
22 unusually rich command set that provides both high-level operations
23 and full access to internals.
25 See linkgit:gittutorial[7] to get started, then see
26 linkgit:giteveryday[7] for a useful minimum set of
27 commands. The link:user-manual.html[Git User's Manual] has a more
28 in-depth introduction.
30 After you mastered the basic concepts, you can come back to this
31 page to learn what commands Git offers. You can learn more about
32 individual Git commands with "git help command". linkgit:gitcli[7]
33 manual page gives you an overview of the command-line command syntax.
35 A formatted and hyperlinked copy of the latest Git documentation
36 can be viewed at `https://git.github.io/htmldocs/git.html`.
42 You are reading the documentation for the latest (possibly
43 unreleased) version of Git, that is available from the 'master'
44 branch of the `git.git` repository.
45 Documentation for older releases are available here:
47 * link:v2.11.0/git.html[documentation for release 2.11]
50 link:RelNotes/2.11.0.txt[2.11].
52 * link:v2.10.2/git.html[documentation for release 2.10.2]
55 link:RelNotes/2.10.2.txt[2.10.2],
56 link:RelNotes/2.10.1.txt[2.10.1],
57 link:RelNotes/2.10.0.txt[2.10].
59 * link:v2.9.3/git.html[documentation for release 2.9.3]
62 link:RelNotes/2.9.3.txt[2.9.3],
63 link:RelNotes/2.9.2.txt[2.9.2],
64 link:RelNotes/2.9.1.txt[2.9.1],
65 link:RelNotes/2.9.0.txt[2.9].
67 * link:v2.8.4/git.html[documentation for release 2.8.4]
70 link:RelNotes/2.8.4.txt[2.8.4],
71 link:RelNotes/2.8.3.txt[2.8.3],
72 link:RelNotes/2.8.2.txt[2.8.2],
73 link:RelNotes/2.8.1.txt[2.8.1],
74 link:RelNotes/2.8.0.txt[2.8].
76 * link:v2.7.3/git.html[documentation for release 2.7.3]
79 link:RelNotes/2.7.3.txt[2.7.3],
80 link:RelNotes/2.7.2.txt[2.7.2],
81 link:RelNotes/2.7.1.txt[2.7.1],
82 link:RelNotes/2.7.0.txt[2.7].
84 * link:v2.6.6/git.html[documentation for release 2.6.6]
87 link:RelNotes/2.6.6.txt[2.6.6],
88 link:RelNotes/2.6.5.txt[2.6.5],
89 link:RelNotes/2.6.4.txt[2.6.4],
90 link:RelNotes/2.6.3.txt[2.6.3],
91 link:RelNotes/2.6.2.txt[2.6.2],
92 link:RelNotes/2.6.1.txt[2.6.1],
93 link:RelNotes/2.6.0.txt[2.6].
95 * link:v2.5.5/git.html[documentation for release 2.5.5]
98 link:RelNotes/2.5.5.txt[2.5.5],
99 link:RelNotes/2.5.4.txt[2.5.4],
100 link:RelNotes/2.5.3.txt[2.5.3],
101 link:RelNotes/2.5.2.txt[2.5.2],
102 link:RelNotes/2.5.1.txt[2.5.1],
103 link:RelNotes/2.5.0.txt[2.5].
105 * link:v2.4.11/git.html[documentation for release 2.4.11]
108 link:RelNotes/2.4.11.txt[2.4.11],
109 link:RelNotes/2.4.10.txt[2.4.10],
110 link:RelNotes/2.4.9.txt[2.4.9],
111 link:RelNotes/2.4.8.txt[2.4.8],
112 link:RelNotes/2.4.7.txt[2.4.7],
113 link:RelNotes/2.4.6.txt[2.4.6],
114 link:RelNotes/2.4.5.txt[2.4.5],
115 link:RelNotes/2.4.4.txt[2.4.4],
116 link:RelNotes/2.4.3.txt[2.4.3],
117 link:RelNotes/2.4.2.txt[2.4.2],
118 link:RelNotes/2.4.1.txt[2.4.1],
119 link:RelNotes/2.4.0.txt[2.4].
121 * link:v2.3.10/git.html[documentation for release 2.3.10]
124 link:RelNotes/2.3.10.txt[2.3.10],
125 link:RelNotes/2.3.9.txt[2.3.9],
126 link:RelNotes/2.3.8.txt[2.3.8],
127 link:RelNotes/2.3.7.txt[2.3.7],
128 link:RelNotes/2.3.6.txt[2.3.6],
129 link:RelNotes/2.3.5.txt[2.3.5],
130 link:RelNotes/2.3.4.txt[2.3.4],
131 link:RelNotes/2.3.3.txt[2.3.3],
132 link:RelNotes/2.3.2.txt[2.3.2],
133 link:RelNotes/2.3.1.txt[2.3.1],
134 link:RelNotes/2.3.0.txt[2.3].
136 * link:v2.2.3/git.html[documentation for release 2.2.3]
139 link:RelNotes/2.2.3.txt[2.2.3],
140 link:RelNotes/2.2.2.txt[2.2.2],
141 link:RelNotes/2.2.1.txt[2.2.1],
142 link:RelNotes/2.2.0.txt[2.2].
144 * link:v2.1.4/git.html[documentation for release 2.1.4]
147 link:RelNotes/2.1.4.txt[2.1.4],
148 link:RelNotes/2.1.3.txt[2.1.3],
149 link:RelNotes/2.1.2.txt[2.1.2],
150 link:RelNotes/2.1.1.txt[2.1.1],
151 link:RelNotes/2.1.0.txt[2.1].
153 * link:v2.0.5/git.html[documentation for release 2.0.5]
156 link:RelNotes/2.0.5.txt[2.0.5],
157 link:RelNotes/2.0.4.txt[2.0.4],
158 link:RelNotes/2.0.3.txt[2.0.3],
159 link:RelNotes/2.0.2.txt[2.0.2],
160 link:RelNotes/2.0.1.txt[2.0.1],
161 link:RelNotes/2.0.0.txt[2.0.0].
163 * link:v1.9.5/git.html[documentation for release 1.9.5]
166 link:RelNotes/1.9.5.txt[1.9.5],
167 link:RelNotes/1.9.4.txt[1.9.4],
168 link:RelNotes/1.9.3.txt[1.9.3],
169 link:RelNotes/1.9.2.txt[1.9.2],
170 link:RelNotes/1.9.1.txt[1.9.1],
171 link:RelNotes/1.9.0.txt[1.9.0].
173 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
176 link:RelNotes/1.8.5.6.txt[1.8.5.6],
177 link:RelNotes/1.8.5.5.txt[1.8.5.5],
178 link:RelNotes/1.8.5.4.txt[1.8.5.4],
179 link:RelNotes/1.8.5.3.txt[1.8.5.3],
180 link:RelNotes/1.8.5.2.txt[1.8.5.2],
181 link:RelNotes/1.8.5.1.txt[1.8.5.1],
182 link:RelNotes/1.8.5.txt[1.8.5].
184 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
187 link:RelNotes/1.8.4.5.txt[1.8.4.5],
188 link:RelNotes/1.8.4.4.txt[1.8.4.4],
189 link:RelNotes/1.8.4.3.txt[1.8.4.3],
190 link:RelNotes/1.8.4.2.txt[1.8.4.2],
191 link:RelNotes/1.8.4.1.txt[1.8.4.1],
192 link:RelNotes/1.8.4.txt[1.8.4].
194 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
197 link:RelNotes/1.8.3.4.txt[1.8.3.4],
198 link:RelNotes/1.8.3.3.txt[1.8.3.3],
199 link:RelNotes/1.8.3.2.txt[1.8.3.2],
200 link:RelNotes/1.8.3.1.txt[1.8.3.1],
201 link:RelNotes/1.8.3.txt[1.8.3].
203 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
206 link:RelNotes/1.8.2.3.txt[1.8.2.3],
207 link:RelNotes/1.8.2.2.txt[1.8.2.2],
208 link:RelNotes/1.8.2.1.txt[1.8.2.1],
209 link:RelNotes/1.8.2.txt[1.8.2].
211 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
214 link:RelNotes/1.8.1.6.txt[1.8.1.6],
215 link:RelNotes/1.8.1.5.txt[1.8.1.5],
216 link:RelNotes/1.8.1.4.txt[1.8.1.4],
217 link:RelNotes/1.8.1.3.txt[1.8.1.3],
218 link:RelNotes/1.8.1.2.txt[1.8.1.2],
219 link:RelNotes/1.8.1.1.txt[1.8.1.1],
220 link:RelNotes/1.8.1.txt[1.8.1].
222 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
225 link:RelNotes/1.8.0.3.txt[1.8.0.3],
226 link:RelNotes/1.8.0.2.txt[1.8.0.2],
227 link:RelNotes/1.8.0.1.txt[1.8.0.1],
228 link:RelNotes/1.8.0.txt[1.8.0].
230 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
233 link:RelNotes/1.7.12.4.txt[1.7.12.4],
234 link:RelNotes/1.7.12.3.txt[1.7.12.3],
235 link:RelNotes/1.7.12.2.txt[1.7.12.2],
236 link:RelNotes/1.7.12.1.txt[1.7.12.1],
237 link:RelNotes/1.7.12.txt[1.7.12].
239 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
242 link:RelNotes/1.7.11.7.txt[1.7.11.7],
243 link:RelNotes/1.7.11.6.txt[1.7.11.6],
244 link:RelNotes/1.7.11.5.txt[1.7.11.5],
245 link:RelNotes/1.7.11.4.txt[1.7.11.4],
246 link:RelNotes/1.7.11.3.txt[1.7.11.3],
247 link:RelNotes/1.7.11.2.txt[1.7.11.2],
248 link:RelNotes/1.7.11.1.txt[1.7.11.1],
249 link:RelNotes/1.7.11.txt[1.7.11].
251 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
254 link:RelNotes/1.7.10.5.txt[1.7.10.5],
255 link:RelNotes/1.7.10.4.txt[1.7.10.4],
256 link:RelNotes/1.7.10.3.txt[1.7.10.3],
257 link:RelNotes/1.7.10.2.txt[1.7.10.2],
258 link:RelNotes/1.7.10.1.txt[1.7.10.1],
259 link:RelNotes/1.7.10.txt[1.7.10].
261 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
264 link:RelNotes/1.7.9.7.txt[1.7.9.7],
265 link:RelNotes/1.7.9.6.txt[1.7.9.6],
266 link:RelNotes/1.7.9.5.txt[1.7.9.5],
267 link:RelNotes/1.7.9.4.txt[1.7.9.4],
268 link:RelNotes/1.7.9.3.txt[1.7.9.3],
269 link:RelNotes/1.7.9.2.txt[1.7.9.2],
270 link:RelNotes/1.7.9.1.txt[1.7.9.1],
271 link:RelNotes/1.7.9.txt[1.7.9].
273 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
276 link:RelNotes/1.7.8.6.txt[1.7.8.6],
277 link:RelNotes/1.7.8.5.txt[1.7.8.5],
278 link:RelNotes/1.7.8.4.txt[1.7.8.4],
279 link:RelNotes/1.7.8.3.txt[1.7.8.3],
280 link:RelNotes/1.7.8.2.txt[1.7.8.2],
281 link:RelNotes/1.7.8.1.txt[1.7.8.1],
282 link:RelNotes/1.7.8.txt[1.7.8].
284 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
287 link:RelNotes/1.7.7.7.txt[1.7.7.7],
288 link:RelNotes/1.7.7.6.txt[1.7.7.6],
289 link:RelNotes/1.7.7.5.txt[1.7.7.5],
290 link:RelNotes/1.7.7.4.txt[1.7.7.4],
291 link:RelNotes/1.7.7.3.txt[1.7.7.3],
292 link:RelNotes/1.7.7.2.txt[1.7.7.2],
293 link:RelNotes/1.7.7.1.txt[1.7.7.1],
294 link:RelNotes/1.7.7.txt[1.7.7].
296 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
299 link:RelNotes/1.7.6.6.txt[1.7.6.6],
300 link:RelNotes/1.7.6.5.txt[1.7.6.5],
301 link:RelNotes/1.7.6.4.txt[1.7.6.4],
302 link:RelNotes/1.7.6.3.txt[1.7.6.3],
303 link:RelNotes/1.7.6.2.txt[1.7.6.2],
304 link:RelNotes/1.7.6.1.txt[1.7.6.1],
305 link:RelNotes/1.7.6.txt[1.7.6].
307 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
310 link:RelNotes/1.7.5.4.txt[1.7.5.4],
311 link:RelNotes/1.7.5.3.txt[1.7.5.3],
312 link:RelNotes/1.7.5.2.txt[1.7.5.2],
313 link:RelNotes/1.7.5.1.txt[1.7.5.1],
314 link:RelNotes/1.7.5.txt[1.7.5].
316 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
319 link:RelNotes/1.7.4.5.txt[1.7.4.5],
320 link:RelNotes/1.7.4.4.txt[1.7.4.4],
321 link:RelNotes/1.7.4.3.txt[1.7.4.3],
322 link:RelNotes/1.7.4.2.txt[1.7.4.2],
323 link:RelNotes/1.7.4.1.txt[1.7.4.1],
324 link:RelNotes/1.7.4.txt[1.7.4].
326 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
329 link:RelNotes/1.7.3.5.txt[1.7.3.5],
330 link:RelNotes/1.7.3.4.txt[1.7.3.4],
331 link:RelNotes/1.7.3.3.txt[1.7.3.3],
332 link:RelNotes/1.7.3.2.txt[1.7.3.2],
333 link:RelNotes/1.7.3.1.txt[1.7.3.1],
334 link:RelNotes/1.7.3.txt[1.7.3].
336 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
339 link:RelNotes/1.7.2.5.txt[1.7.2.5],
340 link:RelNotes/1.7.2.4.txt[1.7.2.4],
341 link:RelNotes/1.7.2.3.txt[1.7.2.3],
342 link:RelNotes/1.7.2.2.txt[1.7.2.2],
343 link:RelNotes/1.7.2.1.txt[1.7.2.1],
344 link:RelNotes/1.7.2.txt[1.7.2].
346 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
349 link:RelNotes/1.7.1.4.txt[1.7.1.4],
350 link:RelNotes/1.7.1.3.txt[1.7.1.3],
351 link:RelNotes/1.7.1.2.txt[1.7.1.2],
352 link:RelNotes/1.7.1.1.txt[1.7.1.1],
353 link:RelNotes/1.7.1.txt[1.7.1].
355 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
358 link:RelNotes/1.7.0.9.txt[1.7.0.9],
359 link:RelNotes/1.7.0.8.txt[1.7.0.8],
360 link:RelNotes/1.7.0.7.txt[1.7.0.7],
361 link:RelNotes/1.7.0.6.txt[1.7.0.6],
362 link:RelNotes/1.7.0.5.txt[1.7.0.5],
363 link:RelNotes/1.7.0.4.txt[1.7.0.4],
364 link:RelNotes/1.7.0.3.txt[1.7.0.3],
365 link:RelNotes/1.7.0.2.txt[1.7.0.2],
366 link:RelNotes/1.7.0.1.txt[1.7.0.1],
367 link:RelNotes/1.7.0.txt[1.7.0].
369 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
372 link:RelNotes/1.6.6.3.txt[1.6.6.3],
373 link:RelNotes/1.6.6.2.txt[1.6.6.2],
374 link:RelNotes/1.6.6.1.txt[1.6.6.1],
375 link:RelNotes/1.6.6.txt[1.6.6].
377 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
380 link:RelNotes/1.6.5.9.txt[1.6.5.9],
381 link:RelNotes/1.6.5.8.txt[1.6.5.8],
382 link:RelNotes/1.6.5.7.txt[1.6.5.7],
383 link:RelNotes/1.6.5.6.txt[1.6.5.6],
384 link:RelNotes/1.6.5.5.txt[1.6.5.5],
385 link:RelNotes/1.6.5.4.txt[1.6.5.4],
386 link:RelNotes/1.6.5.3.txt[1.6.5.3],
387 link:RelNotes/1.6.5.2.txt[1.6.5.2],
388 link:RelNotes/1.6.5.1.txt[1.6.5.1],
389 link:RelNotes/1.6.5.txt[1.6.5].
391 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
394 link:RelNotes/1.6.4.5.txt[1.6.4.5],
395 link:RelNotes/1.6.4.4.txt[1.6.4.4],
396 link:RelNotes/1.6.4.3.txt[1.6.4.3],
397 link:RelNotes/1.6.4.2.txt[1.6.4.2],
398 link:RelNotes/1.6.4.1.txt[1.6.4.1],
399 link:RelNotes/1.6.4.txt[1.6.4].
401 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
404 link:RelNotes/1.6.3.4.txt[1.6.3.4],
405 link:RelNotes/1.6.3.3.txt[1.6.3.3],
406 link:RelNotes/1.6.3.2.txt[1.6.3.2],
407 link:RelNotes/1.6.3.1.txt[1.6.3.1],
408 link:RelNotes/1.6.3.txt[1.6.3].
411 link:RelNotes/1.6.2.5.txt[1.6.2.5],
412 link:RelNotes/1.6.2.4.txt[1.6.2.4],
413 link:RelNotes/1.6.2.3.txt[1.6.2.3],
414 link:RelNotes/1.6.2.2.txt[1.6.2.2],
415 link:RelNotes/1.6.2.1.txt[1.6.2.1],
416 link:RelNotes/1.6.2.txt[1.6.2].
418 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
421 link:RelNotes/1.6.1.3.txt[1.6.1.3],
422 link:RelNotes/1.6.1.2.txt[1.6.1.2],
423 link:RelNotes/1.6.1.1.txt[1.6.1.1],
424 link:RelNotes/1.6.1.txt[1.6.1].
426 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
429 link:RelNotes/1.6.0.6.txt[1.6.0.6],
430 link:RelNotes/1.6.0.5.txt[1.6.0.5],
431 link:RelNotes/1.6.0.4.txt[1.6.0.4],
432 link:RelNotes/1.6.0.3.txt[1.6.0.3],
433 link:RelNotes/1.6.0.2.txt[1.6.0.2],
434 link:RelNotes/1.6.0.1.txt[1.6.0.1],
435 link:RelNotes/1.6.0.txt[1.6.0].
437 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
440 link:RelNotes/1.5.6.6.txt[1.5.6.6],
441 link:RelNotes/1.5.6.5.txt[1.5.6.5],
442 link:RelNotes/1.5.6.4.txt[1.5.6.4],
443 link:RelNotes/1.5.6.3.txt[1.5.6.3],
444 link:RelNotes/1.5.6.2.txt[1.5.6.2],
445 link:RelNotes/1.5.6.1.txt[1.5.6.1],
446 link:RelNotes/1.5.6.txt[1.5.6].
448 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
451 link:RelNotes/1.5.5.6.txt[1.5.5.6],
452 link:RelNotes/1.5.5.5.txt[1.5.5.5],
453 link:RelNotes/1.5.5.4.txt[1.5.5.4],
454 link:RelNotes/1.5.5.3.txt[1.5.5.3],
455 link:RelNotes/1.5.5.2.txt[1.5.5.2],
456 link:RelNotes/1.5.5.1.txt[1.5.5.1],
457 link:RelNotes/1.5.5.txt[1.5.5].
459 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
462 link:RelNotes/1.5.4.7.txt[1.5.4.7],
463 link:RelNotes/1.5.4.6.txt[1.5.4.6],
464 link:RelNotes/1.5.4.5.txt[1.5.4.5],
465 link:RelNotes/1.5.4.4.txt[1.5.4.4],
466 link:RelNotes/1.5.4.3.txt[1.5.4.3],
467 link:RelNotes/1.5.4.2.txt[1.5.4.2],
468 link:RelNotes/1.5.4.1.txt[1.5.4.1],
469 link:RelNotes/1.5.4.txt[1.5.4].
471 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
474 link:RelNotes/1.5.3.8.txt[1.5.3.8],
475 link:RelNotes/1.5.3.7.txt[1.5.3.7],
476 link:RelNotes/1.5.3.6.txt[1.5.3.6],
477 link:RelNotes/1.5.3.5.txt[1.5.3.5],
478 link:RelNotes/1.5.3.4.txt[1.5.3.4],
479 link:RelNotes/1.5.3.3.txt[1.5.3.3],
480 link:RelNotes/1.5.3.2.txt[1.5.3.2],
481 link:RelNotes/1.5.3.1.txt[1.5.3.1],
482 link:RelNotes/1.5.3.txt[1.5.3].
484 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
487 link:RelNotes/1.5.2.5.txt[1.5.2.5],
488 link:RelNotes/1.5.2.4.txt[1.5.2.4],
489 link:RelNotes/1.5.2.3.txt[1.5.2.3],
490 link:RelNotes/1.5.2.2.txt[1.5.2.2],
491 link:RelNotes/1.5.2.1.txt[1.5.2.1],
492 link:RelNotes/1.5.2.txt[1.5.2].
494 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
497 link:RelNotes/1.5.1.6.txt[1.5.1.6],
498 link:RelNotes/1.5.1.5.txt[1.5.1.5],
499 link:RelNotes/1.5.1.4.txt[1.5.1.4],
500 link:RelNotes/1.5.1.3.txt[1.5.1.3],
501 link:RelNotes/1.5.1.2.txt[1.5.1.2],
502 link:RelNotes/1.5.1.1.txt[1.5.1.1],
503 link:RelNotes/1.5.1.txt[1.5.1].
505 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
508 link:RelNotes/1.5.0.7.txt[1.5.0.7],
509 link:RelNotes/1.5.0.6.txt[1.5.0.6],
510 link:RelNotes/1.5.0.5.txt[1.5.0.5],
511 link:RelNotes/1.5.0.3.txt[1.5.0.3],
512 link:RelNotes/1.5.0.2.txt[1.5.0.2],
513 link:RelNotes/1.5.0.1.txt[1.5.0.1],
514 link:RelNotes/1.5.0.txt[1.5.0].
516 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
517 link:v1.3.3/git.html[1.3.3],
518 link:v1.2.6/git.html[1.2.6],
519 link:v1.0.13/git.html[1.0.13].
528 Prints the Git suite version that the 'git' program came from.
531 Prints the synopsis and a list of the most commonly used
532 commands. If the option `--all` or `-a` is given then all
533 available commands are printed. If a Git command is named this
534 option will bring up the manual page for that command.
536 Other options are available to control how the manual page is
537 displayed. See linkgit:git-help[1] for more information,
538 because `git --help ...` is converted internally into `git
542 Run as if git was started in '<path>' instead of the current working
543 directory. When multiple `-C` options are given, each subsequent
544 non-absolute `-C <path>` is interpreted relative to the preceding `-C
547 This option affects options that expect path name like `--git-dir` and
548 `--work-tree` in that their interpretations of the path names would be
549 made relative to the working directory caused by the `-C` option. For
550 example the following invocations are equivalent:
552 git --git-dir=a.git --work-tree=b -C c status
553 git --git-dir=c/a.git --work-tree=c/b status
556 Pass a configuration parameter to the command. The value
557 given will override values from configuration files.
558 The <name> is expected in the same format as listed by
559 'git config' (subkeys separated by dots).
561 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
562 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
563 config file). Including the equals but with an empty value (like `git -c
564 foo.bar= ...`) sets `foo.bar` to the empty string.
566 --exec-path[=<path>]::
567 Path to wherever your core Git programs are installed.
568 This can also be controlled by setting the GIT_EXEC_PATH
569 environment variable. If no path is given, 'git' will print
570 the current setting and then exit.
573 Print the path, without trailing slash, where Git's HTML
574 documentation is installed and exit.
577 Print the manpath (see `man(1)`) for the man pages for
578 this version of Git and exit.
581 Print the path where the Info files documenting this
582 version of Git are installed and exit.
586 Pipe all output into 'less' (or if set, $PAGER) if standard
587 output is a terminal. This overrides the `pager.<cmd>`
588 configuration options (see the "Configuration Mechanism" section
592 Do not pipe Git output into a pager.
595 Set the path to the repository. This can also be controlled by
596 setting the `GIT_DIR` environment variable. It can be an absolute
597 path or relative path to current working directory.
600 Set the path to the working tree. It can be an absolute path
601 or a path relative to the current working directory.
602 This can also be controlled by setting the GIT_WORK_TREE
603 environment variable and the core.worktree configuration
604 variable (see core.worktree in linkgit:git-config[1] for a
605 more detailed discussion).
608 Set the Git namespace. See linkgit:gitnamespaces[7] for more
609 details. Equivalent to setting the `GIT_NAMESPACE` environment
612 --super-prefix=<path>::
613 Currently for internal use only. Set a prefix which gives a path from
614 above a repository down to its root. One use is to give submodules
615 context about the superproject that invoked it.
618 Treat the repository as a bare repository. If GIT_DIR
619 environment is not set, it is set to the current working
622 --no-replace-objects::
623 Do not use replacement refs to replace Git objects. See
624 linkgit:git-replace[1] for more information.
626 --literal-pathspecs::
627 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
628 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
632 Add "glob" magic to all pathspec. This is equivalent to setting
633 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
634 globbing on individual pathspecs can be done using pathspec
638 Add "literal" magic to all pathspec. This is equivalent to setting
639 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
640 globbing on individual pathspecs can be done using pathspec
644 Add "icase" magic to all pathspec. This is equivalent to setting
645 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
650 We divide Git into high level ("porcelain") commands and low level
651 ("plumbing") commands.
653 High-level commands (porcelain)
654 -------------------------------
656 We separate the porcelain commands into the main commands and some
657 ancillary user utilities.
659 Main porcelain commands
660 ~~~~~~~~~~~~~~~~~~~~~~~
662 include::cmds-mainporcelain.txt[]
668 include::cmds-ancillarymanipulators.txt[]
672 include::cmds-ancillaryinterrogators.txt[]
675 Interacting with Others
676 ~~~~~~~~~~~~~~~~~~~~~~~
678 These commands are to interact with foreign SCM and with other
679 people via patch over e-mail.
681 include::cmds-foreignscminterface.txt[]
684 Low-level commands (plumbing)
685 -----------------------------
687 Although Git includes its
688 own porcelain layer, its low-level commands are sufficient to support
689 development of alternative porcelains. Developers of such porcelains
690 might start by reading about linkgit:git-update-index[1] and
691 linkgit:git-read-tree[1].
693 The interface (input, output, set of options and the semantics)
694 to these low-level commands are meant to be a lot more stable
695 than Porcelain level commands, because these commands are
696 primarily for scripted use. The interface to Porcelain commands
697 on the other hand are subject to change in order to improve the
700 The following description divides
701 the low-level commands into commands that manipulate objects (in
702 the repository, index, and working tree), commands that interrogate and
703 compare objects, and commands that move objects and references between
707 Manipulation commands
708 ~~~~~~~~~~~~~~~~~~~~~
710 include::cmds-plumbingmanipulators.txt[]
713 Interrogation commands
714 ~~~~~~~~~~~~~~~~~~~~~~
716 include::cmds-plumbinginterrogators.txt[]
718 In general, the interrogate commands do not touch the files in
722 Synching repositories
723 ~~~~~~~~~~~~~~~~~~~~~
725 include::cmds-synchingrepositories.txt[]
727 The following are helper commands used by the above; end users
728 typically do not use them directly.
730 include::cmds-synchelpers.txt[]
733 Internal helper commands
734 ~~~~~~~~~~~~~~~~~~~~~~~~
736 These are internal helper commands used by other commands; end
737 users typically do not use them directly.
739 include::cmds-purehelpers.txt[]
742 Configuration Mechanism
743 -----------------------
745 Git uses a simple text format to store customizations that are per
746 repository and are per user. Such a configuration file may look
751 # A '#' or ';' character indicates a comment.
756 ; Don't trust file modes
761 name = "Junio C Hamano"
762 email = "gitster@pobox.com"
766 Various commands read from the configuration file and adjust
767 their operation accordingly. See linkgit:git-config[1] for a
768 list and more details about the configuration mechanism.
771 Identifier Terminology
772 ----------------------
774 Indicates the object name for any type of object.
777 Indicates a blob object name.
780 Indicates a tree object name.
783 Indicates a commit object name.
786 Indicates a tree, commit or tag object name. A
787 command that takes a <tree-ish> argument ultimately wants to
788 operate on a <tree> object but automatically dereferences
789 <commit> and <tag> objects that point at a <tree>.
792 Indicates a commit or tag object name. A
793 command that takes a <commit-ish> argument ultimately wants to
794 operate on a <commit> object but automatically dereferences
795 <tag> objects that point at a <commit>.
798 Indicates that an object type is required.
799 Currently one of: `blob`, `tree`, `commit`, or `tag`.
802 Indicates a filename - almost always relative to the
803 root of the tree structure `GIT_INDEX_FILE` describes.
807 Any Git command accepting any <object> can also use the following
811 indicates the head of the current branch.
815 (i.e. a `refs/tags/<tag>` reference).
819 (i.e. a `refs/heads/<head>` reference).
821 For a more complete list of ways to spell object names, see
822 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
825 File/Directory Structure
826 ------------------------
828 Please see the linkgit:gitrepository-layout[5] document.
830 Read linkgit:githooks[5] for more details about each hook.
832 Higher level SCMs may provide and manage additional information in the
838 Please see linkgit:gitglossary[7].
841 Environment Variables
842 ---------------------
843 Various Git commands use the following environment variables:
847 These environment variables apply to 'all' core Git commands. Nb: it
848 is worth noting that they may be used/overridden by SCMS sitting above
849 Git so take care if using a foreign front-end.
852 This environment allows the specification of an alternate
853 index file. If not specified, the default of `$GIT_DIR/index`
856 `GIT_INDEX_VERSION`::
857 This environment variable allows the specification of an index
858 version for new repositories. It won't affect existing index
859 files. By default index file version 2 or 3 is used. See
860 linkgit:git-update-index[1] for more information.
862 `GIT_OBJECT_DIRECTORY`::
863 If the object storage directory is specified via this
864 environment variable then the sha1 directories are created
865 underneath - otherwise the default `$GIT_DIR/objects`
868 `GIT_ALTERNATE_OBJECT_DIRECTORIES`::
869 Due to the immutable nature of Git objects, old objects can be
870 archived into shared, read-only directories. This variable
871 specifies a ":" separated (on Windows ";" separated) list
872 of Git object directories which can be used to search for Git
873 objects. New objects will not be written to these directories.
875 Entries that begin with `"` (double-quote) will be interpreted
876 as C-style quoted paths, removing leading and trailing
877 double-quotes and respecting backslash escapes. E.g., the value
878 `"path-with-\"-and-:-in-it":vanilla-path` has two paths:
879 `path-with-"-and-:-in-it` and `vanilla-path`.
882 If the `GIT_DIR` environment variable is set then it
883 specifies a path to use instead of the default `.git`
884 for the base of the repository.
885 The `--git-dir` command-line option also sets this value.
888 Set the path to the root of the working tree.
889 This can also be controlled by the `--work-tree` command-line
890 option and the core.worktree configuration variable.
893 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
894 The `--namespace` command-line option also sets this value.
896 `GIT_CEILING_DIRECTORIES`::
897 This should be a colon-separated list of absolute paths. If
898 set, it is a list of directories that Git should not chdir up
899 into while looking for a repository directory (useful for
900 excluding slow-loading network directories). It will not
901 exclude the current working directory or a GIT_DIR set on the
902 command line or in the environment. Normally, Git has to read
903 the entries in this list and resolve any symlink that
904 might be present in order to compare them with the current
905 directory. However, if even this access is slow, you
906 can add an empty entry to the list to tell Git that the
907 subsequent entries are not symlinks and needn't be resolved;
909 `GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink`.
911 `GIT_DISCOVERY_ACROSS_FILESYSTEM`::
912 When run in a directory that does not have ".git" repository
913 directory, Git tries to find such a directory in the parent
914 directories to find the top of the working tree, but by default it
915 does not cross filesystem boundaries. This environment variable
916 can be set to true to tell Git not to stop at filesystem
917 boundaries. Like `GIT_CEILING_DIRECTORIES`, this will not affect
918 an explicit repository directory set via `GIT_DIR` or on the
922 If this variable is set to a path, non-worktree files that are
923 normally in $GIT_DIR will be taken from this path
924 instead. Worktree-specific files such as HEAD or index are
925 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
926 linkgit:git-worktree[1] for
927 details. This variable has lower precedence than other path
928 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
935 `GIT_COMMITTER_NAME`::
936 `GIT_COMMITTER_EMAIL`::
937 `GIT_COMMITTER_DATE`::
939 see linkgit:git-commit-tree[1]
944 Only valid setting is "--unified=??" or "-u??" to set the
945 number of context lines shown when a unified diff is created.
946 This takes precedence over any "-U" or "--unified" option
947 value passed on the Git diff command line.
949 `GIT_EXTERNAL_DIFF`::
950 When the environment variable `GIT_EXTERNAL_DIFF` is set, the
951 program named by it is called, instead of the diff invocation
952 described above. For a path that is added, removed, or modified,
953 `GIT_EXTERNAL_DIFF` is called with 7 parameters:
955 path old-file old-hex old-mode new-file new-hex new-mode
959 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
960 contents of <old|new>,
961 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
962 <old|new>-mode:: are the octal representation of the file modes.
964 The file parameters can point at the user's working file
965 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
966 when a new file is added), or a temporary file (e.g. `old-file` in the
967 index). `GIT_EXTERNAL_DIFF` should not worry about unlinking the
968 temporary file --- it is removed when `GIT_EXTERNAL_DIFF` exits.
970 For a path that is unmerged, `GIT_EXTERNAL_DIFF` is called with 1
973 For each path `GIT_EXTERNAL_DIFF` is called, two environment variables,
974 `GIT_DIFF_PATH_COUNTER` and `GIT_DIFF_PATH_TOTAL` are set.
976 `GIT_DIFF_PATH_COUNTER`::
977 A 1-based counter incremented by one for every path.
979 `GIT_DIFF_PATH_TOTAL`::
980 The total number of paths.
984 `GIT_MERGE_VERBOSITY`::
985 A number controlling the amount of output shown by
986 the recursive merge strategy. Overrides merge.verbosity.
987 See linkgit:git-merge[1]
990 This environment variable overrides `$PAGER`. If it is set
991 to an empty string or to the value "cat", Git will not launch
992 a pager. See also the `core.pager` option in
993 linkgit:git-config[1].
996 This environment variable overrides `$EDITOR` and `$VISUAL`.
997 It is used by several Git commands when, on interactive mode,
998 an editor is to be launched. See also linkgit:git-var[1]
999 and the `core.editor` option in linkgit:git-config[1].
1003 If either of these environment variables is set then 'git fetch'
1004 and 'git push' will use the specified command instead of 'ssh'
1005 when they need to connect to a remote system.
1006 The command will be given exactly two or four arguments: the
1007 'username@host' (or just 'host') from the URL and the shell
1008 command to execute on that remote system, optionally preceded by
1009 `-p` (literally) and the 'port' from the URL when it specifies
1010 something other than the default SSH port.
1012 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
1013 by the shell, which allows additional arguments to be included.
1014 `$GIT_SSH` on the other hand must be just the path to a program
1015 (which can be a wrapper shell script, if additional arguments are
1018 Usually it is easier to configure any desired options through your
1019 personal `.ssh/config` file. Please consult your ssh documentation
1020 for further details.
1023 If this environment variable is set, then Git commands which need to
1024 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
1025 will call this program with a suitable prompt as command-line argument
1026 and read the password from its STDOUT. See also the `core.askPass`
1027 option in linkgit:git-config[1].
1029 `GIT_TERMINAL_PROMPT`::
1030 If this environment variable is set to `0`, git will not prompt
1031 on the terminal (e.g., when asking for HTTP authentication).
1033 `GIT_CONFIG_NOSYSTEM`::
1034 Whether to skip reading settings from the system-wide
1035 `$(prefix)/etc/gitconfig` file. This environment variable can
1036 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
1037 predictable environment for a picky script, or you can set it
1038 temporarily to avoid using a buggy `/etc/gitconfig` file while
1039 waiting for someone with sufficient permissions to fix it.
1042 If this environment variable is set to "1", then commands such
1043 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
1044 'git check-attr' and 'git check-ignore' will
1045 force a flush of the output stream after each record have been
1047 variable is set to "0", the output of these commands will be done
1048 using completely buffered I/O. If this environment variable is
1049 not set, Git will choose buffered or record-oriented flushing
1050 based on whether stdout appears to be redirected to a file or not.
1053 Enables general trace messages, e.g. alias expansion, built-in
1054 command execution and external command execution.
1056 If this variable is set to "1", "2" or "true" (comparison
1057 is case insensitive), trace messages will be printed to
1060 If the variable is set to an integer value greater than 2
1061 and lower than 10 (strictly) then Git will interpret this
1062 value as an open file descriptor and will try to write the
1063 trace messages into this file descriptor.
1065 Alternatively, if the variable is set to an absolute path
1066 (starting with a '/' character), Git will interpret this
1067 as a file path and will try to write the trace messages
1070 Unsetting the variable, or setting it to empty, "0" or
1071 "false" (case insensitive) disables trace messages.
1073 `GIT_TRACE_PACK_ACCESS`::
1074 Enables trace messages for all accesses to any packs. For each
1075 access, the pack file name and an offset in the pack is
1076 recorded. This may be helpful for troubleshooting some
1077 pack-related performance problems.
1078 See `GIT_TRACE` for available trace output options.
1080 `GIT_TRACE_PACKET`::
1081 Enables trace messages for all packets coming in or out of a
1082 given program. This can help with debugging object negotiation
1083 or other protocol issues. Tracing is turned off at a packet
1084 starting with "PACK" (but see `GIT_TRACE_PACKFILE` below).
1085 See `GIT_TRACE` for available trace output options.
1087 `GIT_TRACE_PACKFILE`::
1088 Enables tracing of packfiles sent or received by a
1089 given program. Unlike other trace output, this trace is
1090 verbatim: no headers, and no quoting of binary data. You almost
1091 certainly want to direct into a file (e.g.,
1092 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1093 the terminal or mixing it with other trace output.
1095 Note that this is currently only implemented for the client side
1096 of clones and fetches.
1098 `GIT_TRACE_PERFORMANCE`::
1099 Enables performance related trace messages, e.g. total execution
1100 time of each Git command.
1101 See `GIT_TRACE` for available trace output options.
1104 Enables trace messages printing the .git, working tree and current
1105 working directory after Git has completed its setup phase.
1106 See `GIT_TRACE` for available trace output options.
1108 `GIT_TRACE_SHALLOW`::
1109 Enables trace messages that can help debugging fetching /
1110 cloning of shallow repositories.
1111 See `GIT_TRACE` for available trace output options.
1114 Enables a curl full trace dump of all incoming and outgoing data,
1115 including descriptive information, of the git transport protocol.
1116 This is similar to doing curl `--trace-ascii` on the command line.
1117 This option overrides setting the `GIT_CURL_VERBOSE` environment
1119 See `GIT_TRACE` for available trace output options.
1121 `GIT_LITERAL_PATHSPECS`::
1122 Setting this variable to `1` will cause Git to treat all
1123 pathspecs literally, rather than as glob patterns. For example,
1124 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1125 for commits that touch the path `*.c`, not any paths that the
1126 glob `*.c` matches. You might want this if you are feeding
1127 literal paths to Git (e.g., paths previously given to you by
1128 `git ls-tree`, `--raw` diff output, etc).
1130 `GIT_GLOB_PATHSPECS`::
1131 Setting this variable to `1` will cause Git to treat all
1132 pathspecs as glob patterns (aka "glob" magic).
1134 `GIT_NOGLOB_PATHSPECS`::
1135 Setting this variable to `1` will cause Git to treat all
1136 pathspecs as literal (aka "literal" magic).
1138 `GIT_ICASE_PATHSPECS`::
1139 Setting this variable to `1` will cause Git to treat all
1140 pathspecs as case-insensitive.
1142 `GIT_REFLOG_ACTION`::
1143 When a ref is updated, reflog entries are created to keep
1144 track of the reason why the ref was updated (which is
1145 typically the name of the high-level command that updated
1146 the ref), in addition to the old and new values of the ref.
1147 A scripted Porcelain command can use set_reflog_action
1148 helper function in `git-sh-setup` to set its name to this
1149 variable when it is invoked as the top level command by the
1150 end user, to be recorded in the body of the reflog.
1152 `GIT_REF_PARANOIA`::
1153 If set to `1`, include broken or badly named refs when iterating
1154 over lists of refs. In a normal, non-corrupted repository, this
1155 does nothing. However, enabling it may help git to detect and
1156 abort some operations in the presence of broken refs. Git sets
1157 this variable automatically when performing destructive
1158 operations like linkgit:git-prune[1]. You should not need to set
1159 it yourself unless you want to be paranoid about making sure
1160 an operation has touched every ref (e.g., because you are
1161 cloning a repository to make a backup).
1163 `GIT_ALLOW_PROTOCOL`::
1164 If set, provide a colon-separated list of protocols which are
1165 allowed to be used with fetch/push/clone. This is useful to
1166 restrict recursive submodule initialization from an untrusted
1167 repository. Any protocol not mentioned will be disallowed (i.e.,
1168 this is a whitelist, not a blacklist). If the variable is not
1169 set at all, all protocols are enabled. The protocol names
1170 currently used by git are:
1172 - `file`: any local file-based path (including `file://` URLs,
1175 - `git`: the anonymous git protocol over a direct TCP
1176 connection (or proxy, if configured)
1178 - `ssh`: git over ssh (including `host:path` syntax,
1181 - `http`: git over http, both "smart http" and "dumb http".
1182 Note that this does _not_ include `https`; if you want both,
1183 you should specify both as `http:https`.
1185 - any external helpers are named by their protocol (e.g., use
1186 `hg` to allow the `git-remote-hg` helper)
1189 Discussion[[Discussion]]
1190 ------------------------
1192 More detail on the following is available from the
1193 link:user-manual.html#git-concepts[Git concepts chapter of the
1194 user-manual] and linkgit:gitcore-tutorial[7].
1196 A Git project normally consists of a working directory with a ".git"
1197 subdirectory at the top level. The .git directory contains, among other
1198 things, a compressed object database representing the complete history
1199 of the project, an "index" file which links that history to the current
1200 contents of the working tree, and named pointers into that history such
1201 as tags and branch heads.
1203 The object database contains objects of three main types: blobs, which
1204 hold file data; trees, which point to blobs and other trees to build up
1205 directory hierarchies; and commits, which each reference a single tree
1206 and some number of parent commits.
1208 The commit, equivalent to what other systems call a "changeset" or
1209 "version", represents a step in the project's history, and each parent
1210 represents an immediately preceding step. Commits with more than one
1211 parent represent merges of independent lines of development.
1213 All objects are named by the SHA-1 hash of their contents, normally
1214 written as a string of 40 hex digits. Such names are globally unique.
1215 The entire history leading up to a commit can be vouched for by signing
1216 just that commit. A fourth object type, the tag, is provided for this
1219 When first created, objects are stored in individual files, but for
1220 efficiency may later be compressed together into "pack files".
1222 Named pointers called refs mark interesting points in history. A ref
1223 may contain the SHA-1 name of an object or the name of another ref. Refs
1224 with names beginning `ref/head/` contain the SHA-1 name of the most
1225 recent commit (or "head") of a branch under development. SHA-1 names of
1226 tags of interest are stored under `ref/tags/`. A special ref named
1227 `HEAD` contains the name of the currently checked-out branch.
1229 The index file is initialized with a list of all paths and, for each
1230 path, a blob object and a set of attributes. The blob object represents
1231 the contents of the file as of the head of the current branch. The
1232 attributes (last modified time, size, etc.) are taken from the
1233 corresponding file in the working tree. Subsequent changes to the
1234 working tree can be found by comparing these attributes. The index may
1235 be updated with new content, and new commits may be created from the
1236 content stored in the index.
1238 The index is also capable of storing multiple entries (called "stages")
1239 for a given pathname. These stages are used to hold the various
1240 unmerged version of a file when a merge is in progress.
1242 FURTHER DOCUMENTATION
1243 ---------------------
1245 See the references in the "description" section to get started
1246 using Git. The following is probably more detail than necessary
1247 for a first-time user.
1249 The link:user-manual.html#git-concepts[Git concepts chapter of the
1250 user-manual] and linkgit:gitcore-tutorial[7] both provide
1251 introductions to the underlying Git architecture.
1253 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1255 See also the link:howto-index.html[howto] documents for some useful
1258 The internals are documented in the
1259 link:technical/api-index.html[Git API documentation].
1261 Users migrating from CVS may also want to
1262 read linkgit:gitcvs-migration[7].
1267 Git was started by Linus Torvalds, and is currently maintained by Junio
1268 C Hamano. Numerous contributions have come from the Git mailing list
1269 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1270 gives you a more complete list of contributors.
1272 If you have a clone of git.git itself, the
1273 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1274 the authors for specific parts of the project.
1279 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1280 development and maintenance is primarily done. You do not have to be
1281 subscribed to the list to send a message there.
1285 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1286 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1287 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1288 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1289 linkgit:gitworkflows[7]
1293 Part of the linkgit:git[1] suite