GIT 1.6.4.2
[git/git.git] / Documentation / git.txt
1 git(1)
2 ======
3
4 NAME
5 ----
6 git - the stupid content tracker
7
8
9 SYNOPSIS
10 --------
11 [verse]
12 'git' [--version] [--exec-path[=GIT_EXEC_PATH]] [--html-path]
13 [-p|--paginate|--no-pager]
14 [--bare] [--git-dir=GIT_DIR] [--work-tree=GIT_WORK_TREE]
15 [--help] COMMAND [ARGS]
16
17 DESCRIPTION
18 -----------
19 Git is a fast, scalable, distributed revision control system with an
20 unusually rich command set that provides both high-level operations
21 and full access to internals.
22
23 See linkgit:gittutorial[7] to get started, then see
24 link:everyday.html[Everyday Git] for a useful minimum set of commands, and
25 "man git-commandname" for documentation of each command. CVS users may
26 also want to read linkgit:gitcvs-migration[7]. See
27 the link:user-manual.html[Git User's Manual] for a more in-depth
28 introduction.
29
30 The COMMAND is either a name of a Git command (see below) or an alias
31 as defined in the configuration file (see linkgit:git-config[1]).
32
33 Formatted and hyperlinked version of the latest git
34 documentation can be viewed at
35 `http://www.kernel.org/pub/software/scm/git/docs/`.
36
37 ifdef::stalenotes[]
38 [NOTE]
39 ============
40
41 You are reading the documentation for the latest (possibly
42 unreleased) version of git, that is available from 'master'
43 branch of the `git.git` repository.
44 Documentation for older releases are available here:
45
46 * link:v1.6.4.2/git.html[documentation for release 1.6.4.2]
47
48 * release notes for
49 link:RelNotes-1.6.4.2.txt[1.6.4.2],
50 link:RelNotes-1.6.4.1.txt[1.6.4.1],
51 link:RelNotes-1.6.4.txt[1.6.4].
52
53 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
54
55 * release notes for
56 link:RelNotes-1.6.3.4.txt[1.6.3.4],
57 link:RelNotes-1.6.3.3.txt[1.6.3.3],
58 link:RelNotes-1.6.3.2.txt[1.6.3.2],
59 link:RelNotes-1.6.3.1.txt[1.6.3.1],
60 link:RelNotes-1.6.3.txt[1.6.3].
61
62 * release notes for
63 link:RelNotes-1.6.2.5.txt[1.6.2.5],
64 link:RelNotes-1.6.2.4.txt[1.6.2.4],
65 link:RelNotes-1.6.2.3.txt[1.6.2.3],
66 link:RelNotes-1.6.2.2.txt[1.6.2.2],
67 link:RelNotes-1.6.2.1.txt[1.6.2.1],
68 link:RelNotes-1.6.2.txt[1.6.2].
69
70 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
71
72 * release notes for
73 link:RelNotes-1.6.1.3.txt[1.6.1.3],
74 link:RelNotes-1.6.1.2.txt[1.6.1.2],
75 link:RelNotes-1.6.1.1.txt[1.6.1.1],
76 link:RelNotes-1.6.1.txt[1.6.1].
77
78 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
79
80 * release notes for
81 link:RelNotes-1.6.0.6.txt[1.6.0.6],
82 link:RelNotes-1.6.0.5.txt[1.6.0.5],
83 link:RelNotes-1.6.0.4.txt[1.6.0.4],
84 link:RelNotes-1.6.0.3.txt[1.6.0.3],
85 link:RelNotes-1.6.0.2.txt[1.6.0.2],
86 link:RelNotes-1.6.0.1.txt[1.6.0.1],
87 link:RelNotes-1.6.0.txt[1.6.0].
88
89 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
90
91 * release notes for
92 link:RelNotes-1.5.6.6.txt[1.5.6.6],
93 link:RelNotes-1.5.6.5.txt[1.5.6.5],
94 link:RelNotes-1.5.6.4.txt[1.5.6.4],
95 link:RelNotes-1.5.6.3.txt[1.5.6.3],
96 link:RelNotes-1.5.6.2.txt[1.5.6.2],
97 link:RelNotes-1.5.6.1.txt[1.5.6.1],
98 link:RelNotes-1.5.6.txt[1.5.6].
99
100 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
101
102 * release notes for
103 link:RelNotes-1.5.5.6.txt[1.5.5.6],
104 link:RelNotes-1.5.5.5.txt[1.5.5.5],
105 link:RelNotes-1.5.5.4.txt[1.5.5.4],
106 link:RelNotes-1.5.5.3.txt[1.5.5.3],
107 link:RelNotes-1.5.5.2.txt[1.5.5.2],
108 link:RelNotes-1.5.5.1.txt[1.5.5.1],
109 link:RelNotes-1.5.5.txt[1.5.5].
110
111 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
112
113 * release notes for
114 link:RelNotes-1.5.4.7.txt[1.5.4.7],
115 link:RelNotes-1.5.4.6.txt[1.5.4.6],
116 link:RelNotes-1.5.4.5.txt[1.5.4.5],
117 link:RelNotes-1.5.4.4.txt[1.5.4.4],
118 link:RelNotes-1.5.4.3.txt[1.5.4.3],
119 link:RelNotes-1.5.4.2.txt[1.5.4.2],
120 link:RelNotes-1.5.4.1.txt[1.5.4.1],
121 link:RelNotes-1.5.4.txt[1.5.4].
122
123 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
124
125 * release notes for
126 link:RelNotes-1.5.3.8.txt[1.5.3.8],
127 link:RelNotes-1.5.3.7.txt[1.5.3.7],
128 link:RelNotes-1.5.3.6.txt[1.5.3.6],
129 link:RelNotes-1.5.3.5.txt[1.5.3.5],
130 link:RelNotes-1.5.3.4.txt[1.5.3.4],
131 link:RelNotes-1.5.3.3.txt[1.5.3.3],
132 link:RelNotes-1.5.3.2.txt[1.5.3.2],
133 link:RelNotes-1.5.3.1.txt[1.5.3.1],
134 link:RelNotes-1.5.3.txt[1.5.3].
135
136 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
137
138 * release notes for
139 link:RelNotes-1.5.2.5.txt[1.5.2.5],
140 link:RelNotes-1.5.2.4.txt[1.5.2.4],
141 link:RelNotes-1.5.2.3.txt[1.5.2.3],
142 link:RelNotes-1.5.2.2.txt[1.5.2.2],
143 link:RelNotes-1.5.2.1.txt[1.5.2.1],
144 link:RelNotes-1.5.2.txt[1.5.2].
145
146 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
147
148 * release notes for
149 link:RelNotes-1.5.1.6.txt[1.5.1.6],
150 link:RelNotes-1.5.1.5.txt[1.5.1.5],
151 link:RelNotes-1.5.1.4.txt[1.5.1.4],
152 link:RelNotes-1.5.1.3.txt[1.5.1.3],
153 link:RelNotes-1.5.1.2.txt[1.5.1.2],
154 link:RelNotes-1.5.1.1.txt[1.5.1.1],
155 link:RelNotes-1.5.1.txt[1.5.1].
156
157 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
158
159 * release notes for
160 link:RelNotes-1.5.0.7.txt[1.5.0.7],
161 link:RelNotes-1.5.0.6.txt[1.5.0.6],
162 link:RelNotes-1.5.0.5.txt[1.5.0.5],
163 link:RelNotes-1.5.0.3.txt[1.5.0.3],
164 link:RelNotes-1.5.0.2.txt[1.5.0.2],
165 link:RelNotes-1.5.0.1.txt[1.5.0.1],
166 link:RelNotes-1.5.0.txt[1.5.0].
167
168 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
169 link:v1.3.3/git.html[1.3.3],
170 link:v1.2.6/git.html[1.2.6],
171 link:v1.0.13/git.html[1.0.13].
172
173 ============
174
175 endif::stalenotes[]
176
177 OPTIONS
178 -------
179 --version::
180 Prints the git suite version that the 'git' program came from.
181
182 --help::
183 Prints the synopsis and a list of the most commonly used
184 commands. If the option '--all' or '-a' is given then all
185 available commands are printed. If a git command is named this
186 option will bring up the manual page for that command.
187 +
188 Other options are available to control how the manual page is
189 displayed. See linkgit:git-help[1] for more information,
190 because `git --help ...` is converted internally into `git
191 help ...`.
192
193 --exec-path::
194 Path to wherever your core git programs are installed.
195 This can also be controlled by setting the GIT_EXEC_PATH
196 environment variable. If no path is given, 'git' will print
197 the current setting and then exit.
198
199 --html-path::
200 Print the path to wherever your git HTML documentation is installed
201 and exit.
202
203 -p::
204 --paginate::
205 Pipe all output into 'less' (or if set, $PAGER).
206
207 --no-pager::
208 Do not pipe git output into a pager.
209
210 --git-dir=<path>::
211 Set the path to the repository. This can also be controlled by
212 setting the GIT_DIR environment variable. It can be an absolute
213 path or relative path to current working directory.
214
215 --work-tree=<path>::
216 Set the path to the working tree. The value will not be
217 used in combination with repositories found automatically in
218 a .git directory (i.e. $GIT_DIR is not set).
219 This can also be controlled by setting the GIT_WORK_TREE
220 environment variable and the core.worktree configuration
221 variable. It can be an absolute path or relative path to
222 the directory specified by --git-dir or GIT_DIR.
223 Note: If --git-dir or GIT_DIR are specified but none of
224 --work-tree, GIT_WORK_TREE and core.worktree is specified,
225 the current working directory is regarded as the top directory
226 of your working tree.
227
228 --bare::
229 Treat the repository as a bare repository. If GIT_DIR
230 environment is not set, it is set to the current working
231 directory.
232
233
234 FURTHER DOCUMENTATION
235 ---------------------
236
237 See the references above to get started using git. The following is
238 probably more detail than necessary for a first-time user.
239
240 The link:user-manual.html#git-concepts[git concepts chapter of the
241 user-manual] and linkgit:gitcore-tutorial[7] both provide
242 introductions to the underlying git architecture.
243
244 See linkgit:gitworkflows[7] for an overview of recommended workflows.
245
246 See also the link:howto-index.html[howto] documents for some useful
247 examples.
248
249 The internals are documented in the
250 link:technical/api-index.html[GIT API documentation].
251
252 GIT COMMANDS
253 ------------
254
255 We divide git into high level ("porcelain") commands and low level
256 ("plumbing") commands.
257
258 High-level commands (porcelain)
259 -------------------------------
260
261 We separate the porcelain commands into the main commands and some
262 ancillary user utilities.
263
264 Main porcelain commands
265 ~~~~~~~~~~~~~~~~~~~~~~~
266
267 include::cmds-mainporcelain.txt[]
268
269 Ancillary Commands
270 ~~~~~~~~~~~~~~~~~~
271 Manipulators:
272
273 include::cmds-ancillarymanipulators.txt[]
274
275 Interrogators:
276
277 include::cmds-ancillaryinterrogators.txt[]
278
279
280 Interacting with Others
281 ~~~~~~~~~~~~~~~~~~~~~~~
282
283 These commands are to interact with foreign SCM and with other
284 people via patch over e-mail.
285
286 include::cmds-foreignscminterface.txt[]
287
288
289 Low-level commands (plumbing)
290 -----------------------------
291
292 Although git includes its
293 own porcelain layer, its low-level commands are sufficient to support
294 development of alternative porcelains. Developers of such porcelains
295 might start by reading about linkgit:git-update-index[1] and
296 linkgit:git-read-tree[1].
297
298 The interface (input, output, set of options and the semantics)
299 to these low-level commands are meant to be a lot more stable
300 than Porcelain level commands, because these commands are
301 primarily for scripted use. The interface to Porcelain commands
302 on the other hand are subject to change in order to improve the
303 end user experience.
304
305 The following description divides
306 the low-level commands into commands that manipulate objects (in
307 the repository, index, and working tree), commands that interrogate and
308 compare objects, and commands that move objects and references between
309 repositories.
310
311
312 Manipulation commands
313 ~~~~~~~~~~~~~~~~~~~~~
314
315 include::cmds-plumbingmanipulators.txt[]
316
317
318 Interrogation commands
319 ~~~~~~~~~~~~~~~~~~~~~~
320
321 include::cmds-plumbinginterrogators.txt[]
322
323 In general, the interrogate commands do not touch the files in
324 the working tree.
325
326
327 Synching repositories
328 ~~~~~~~~~~~~~~~~~~~~~
329
330 include::cmds-synchingrepositories.txt[]
331
332 The following are helper commands used by the above; end users
333 typically do not use them directly.
334
335 include::cmds-synchelpers.txt[]
336
337
338 Internal helper commands
339 ~~~~~~~~~~~~~~~~~~~~~~~~
340
341 These are internal helper commands used by other commands; end
342 users typically do not use them directly.
343
344 include::cmds-purehelpers.txt[]
345
346
347 Configuration Mechanism
348 -----------------------
349
350 Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
351 is used to hold per-repository configuration options. It is a
352 simple text file modeled after `.ini` format familiar to some
353 people. Here is an example:
354
355 ------------
356 #
357 # A '#' or ';' character indicates a comment.
358 #
359
360 ; core variables
361 [core]
362 ; Don't trust file modes
363 filemode = false
364
365 ; user identity
366 [user]
367 name = "Junio C Hamano"
368 email = "junkio@twinsun.com"
369
370 ------------
371
372 Various commands read from the configuration file and adjust
373 their operation accordingly.
374
375
376 Identifier Terminology
377 ----------------------
378 <object>::
379 Indicates the object name for any type of object.
380
381 <blob>::
382 Indicates a blob object name.
383
384 <tree>::
385 Indicates a tree object name.
386
387 <commit>::
388 Indicates a commit object name.
389
390 <tree-ish>::
391 Indicates a tree, commit or tag object name. A
392 command that takes a <tree-ish> argument ultimately wants to
393 operate on a <tree> object but automatically dereferences
394 <commit> and <tag> objects that point at a <tree>.
395
396 <commit-ish>::
397 Indicates a commit or tag object name. A
398 command that takes a <commit-ish> argument ultimately wants to
399 operate on a <commit> object but automatically dereferences
400 <tag> objects that point at a <commit>.
401
402 <type>::
403 Indicates that an object type is required.
404 Currently one of: `blob`, `tree`, `commit`, or `tag`.
405
406 <file>::
407 Indicates a filename - almost always relative to the
408 root of the tree structure `GIT_INDEX_FILE` describes.
409
410 Symbolic Identifiers
411 --------------------
412 Any git command accepting any <object> can also use the following
413 symbolic notation:
414
415 HEAD::
416 indicates the head of the current branch (i.e. the
417 contents of `$GIT_DIR/HEAD`).
418
419 <tag>::
420 a valid tag 'name'
421 (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`).
422
423 <head>::
424 a valid head 'name'
425 (i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
426
427 For a more complete list of ways to spell object names, see
428 "SPECIFYING REVISIONS" section in linkgit:git-rev-parse[1].
429
430
431 File/Directory Structure
432 ------------------------
433
434 Please see the linkgit:gitrepository-layout[5] document.
435
436 Read linkgit:githooks[5] for more details about each hook.
437
438 Higher level SCMs may provide and manage additional information in the
439 `$GIT_DIR`.
440
441
442 Terminology
443 -----------
444 Please see linkgit:gitglossary[7].
445
446
447 Environment Variables
448 ---------------------
449 Various git commands use the following environment variables:
450
451 The git Repository
452 ~~~~~~~~~~~~~~~~~~
453 These environment variables apply to 'all' core git commands. Nb: it
454 is worth noting that they may be used/overridden by SCMS sitting above
455 git so take care if using Cogito etc.
456
457 'GIT_INDEX_FILE'::
458 This environment allows the specification of an alternate
459 index file. If not specified, the default of `$GIT_DIR/index`
460 is used.
461
462 'GIT_OBJECT_DIRECTORY'::
463 If the object storage directory is specified via this
464 environment variable then the sha1 directories are created
465 underneath - otherwise the default `$GIT_DIR/objects`
466 directory is used.
467
468 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
469 Due to the immutable nature of git objects, old objects can be
470 archived into shared, read-only directories. This variable
471 specifies a ":" separated (on Windows ";" separated) list
472 of git object directories which can be used to search for git
473 objects. New objects will not be written to these directories.
474
475 'GIT_DIR'::
476 If the 'GIT_DIR' environment variable is set then it
477 specifies a path to use instead of the default `.git`
478 for the base of the repository.
479
480 'GIT_WORK_TREE'::
481 Set the path to the working tree. The value will not be
482 used in combination with repositories found automatically in
483 a .git directory (i.e. $GIT_DIR is not set).
484 This can also be controlled by the '--work-tree' command line
485 option and the core.worktree configuration variable.
486
487 'GIT_CEILING_DIRECTORIES'::
488 This should be a colon-separated list of absolute paths.
489 If set, it is a list of directories that git should not chdir
490 up into while looking for a repository directory.
491 It will not exclude the current working directory or
492 a GIT_DIR set on the command line or in the environment.
493 (Useful for excluding slow-loading network directories.)
494
495 git Commits
496 ~~~~~~~~~~~
497 'GIT_AUTHOR_NAME'::
498 'GIT_AUTHOR_EMAIL'::
499 'GIT_AUTHOR_DATE'::
500 'GIT_COMMITTER_NAME'::
501 'GIT_COMMITTER_EMAIL'::
502 'GIT_COMMITTER_DATE'::
503 'EMAIL'::
504 see linkgit:git-commit-tree[1]
505
506 git Diffs
507 ~~~~~~~~~
508 'GIT_DIFF_OPTS'::
509 Only valid setting is "--unified=??" or "-u??" to set the
510 number of context lines shown when a unified diff is created.
511 This takes precedence over any "-U" or "--unified" option
512 value passed on the git diff command line.
513
514 'GIT_EXTERNAL_DIFF'::
515 When the environment variable 'GIT_EXTERNAL_DIFF' is set, the
516 program named by it is called, instead of the diff invocation
517 described above. For a path that is added, removed, or modified,
518 'GIT_EXTERNAL_DIFF' is called with 7 parameters:
519
520 path old-file old-hex old-mode new-file new-hex new-mode
521 +
522 where:
523
524 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
525 contents of <old|new>,
526 <old|new>-hex:: are the 40-hexdigit SHA1 hashes,
527 <old|new>-mode:: are the octal representation of the file modes.
528
529 +
530 The file parameters can point at the user's working file
531 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
532 when a new file is added), or a temporary file (e.g. `old-file` in the
533 index). 'GIT_EXTERNAL_DIFF' should not worry about unlinking the
534 temporary file --- it is removed when 'GIT_EXTERNAL_DIFF' exits.
535 +
536 For a path that is unmerged, 'GIT_EXTERNAL_DIFF' is called with 1
537 parameter, <path>.
538
539 other
540 ~~~~~
541 'GIT_MERGE_VERBOSITY'::
542 A number controlling the amount of output shown by
543 the recursive merge strategy. Overrides merge.verbosity.
544 See linkgit:git-merge[1]
545
546 'GIT_PAGER'::
547 This environment variable overrides `$PAGER`. If it is set
548 to an empty string or to the value "cat", git will not launch
549 a pager. See also the `core.pager` option in
550 linkgit:git-config[1].
551
552 'GIT_SSH'::
553 If this environment variable is set then 'git-fetch'
554 and 'git-push' will use this command instead
555 of 'ssh' when they need to connect to a remote system.
556 The '$GIT_SSH' command will be given exactly two arguments:
557 the 'username@host' (or just 'host') from the URL and the
558 shell command to execute on that remote system.
559 +
560 To pass options to the program that you want to list in GIT_SSH
561 you will need to wrap the program and options into a shell script,
562 then set GIT_SSH to refer to the shell script.
563 +
564 Usually it is easier to configure any desired options through your
565 personal `.ssh/config` file. Please consult your ssh documentation
566 for further details.
567
568 'GIT_FLUSH'::
569 If this environment variable is set to "1", then commands such
570 as 'git-blame' (in incremental mode), 'git-rev-list', 'git-log',
571 and 'git-whatchanged' will force a flush of the output stream
572 after each commit-oriented record have been flushed. If this
573 variable is set to "0", the output of these commands will be done
574 using completely buffered I/O. If this environment variable is
575 not set, git will choose buffered or record-oriented flushing
576 based on whether stdout appears to be redirected to a file or not.
577
578 'GIT_TRACE'::
579 If this variable is set to "1", "2" or "true" (comparison
580 is case insensitive), git will print `trace:` messages on
581 stderr telling about alias expansion, built-in command
582 execution and external command execution.
583 If this variable is set to an integer value greater than 1
584 and lower than 10 (strictly) then git will interpret this
585 value as an open file descriptor and will try to write the
586 trace messages into this file descriptor.
587 Alternatively, if this variable is set to an absolute path
588 (starting with a '/' character), git will interpret this
589 as a file path and will try to write the trace messages
590 into it.
591
592 Discussion[[Discussion]]
593 ------------------------
594
595 More detail on the following is available from the
596 link:user-manual.html#git-concepts[git concepts chapter of the
597 user-manual] and linkgit:gitcore-tutorial[7].
598
599 A git project normally consists of a working directory with a ".git"
600 subdirectory at the top level. The .git directory contains, among other
601 things, a compressed object database representing the complete history
602 of the project, an "index" file which links that history to the current
603 contents of the working tree, and named pointers into that history such
604 as tags and branch heads.
605
606 The object database contains objects of three main types: blobs, which
607 hold file data; trees, which point to blobs and other trees to build up
608 directory hierarchies; and commits, which each reference a single tree
609 and some number of parent commits.
610
611 The commit, equivalent to what other systems call a "changeset" or
612 "version", represents a step in the project's history, and each parent
613 represents an immediately preceding step. Commits with more than one
614 parent represent merges of independent lines of development.
615
616 All objects are named by the SHA1 hash of their contents, normally
617 written as a string of 40 hex digits. Such names are globally unique.
618 The entire history leading up to a commit can be vouched for by signing
619 just that commit. A fourth object type, the tag, is provided for this
620 purpose.
621
622 When first created, objects are stored in individual files, but for
623 efficiency may later be compressed together into "pack files".
624
625 Named pointers called refs mark interesting points in history. A ref
626 may contain the SHA1 name of an object or the name of another ref. Refs
627 with names beginning `ref/head/` contain the SHA1 name of the most
628 recent commit (or "head") of a branch under development. SHA1 names of
629 tags of interest are stored under `ref/tags/`. A special ref named
630 `HEAD` contains the name of the currently checked-out branch.
631
632 The index file is initialized with a list of all paths and, for each
633 path, a blob object and a set of attributes. The blob object represents
634 the contents of the file as of the head of the current branch. The
635 attributes (last modified time, size, etc.) are taken from the
636 corresponding file in the working tree. Subsequent changes to the
637 working tree can be found by comparing these attributes. The index may
638 be updated with new content, and new commits may be created from the
639 content stored in the index.
640
641 The index is also capable of storing multiple entries (called "stages")
642 for a given pathname. These stages are used to hold the various
643 unmerged version of a file when a merge is in progress.
644
645 Authors
646 -------
647 * git's founding father is Linus Torvalds <torvalds@osdl.org>.
648 * The current git nurse is Junio C Hamano <gitster@pobox.com>.
649 * The git potty was written by Andreas Ericsson <ae@op5.se>.
650 * General upbringing is handled by the git-list <git@vger.kernel.org>.
651
652 Documentation
653 --------------
654 The documentation for git suite was started by David Greaves
655 <david@dgreaves.com>, and later enhanced greatly by the
656 contributors on the git-list <git@vger.kernel.org>.
657
658 SEE ALSO
659 --------
660 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
661 link:everyday.html[Everyday Git], linkgit:gitcvs-migration[7],
662 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
663 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
664 linkgit:gitworkflows[7]
665
666 GIT
667 ---
668 Part of the linkgit:git[1] suite