1GIT(1) Git Manual GIT(1)
2
6 git - the stupid content tracker
7
9 git [--version] [--exec-path[=<path>]] [--html-path]
10 [-p|--paginate|--no-pager] [--no-replace-objects]
11 [--bare] [--git-dir=<path>] [--work-tree=<path>]
12 [-c <name>=<value>]
13 [--help] <command> [<args>]
14
17 Git is a fast, scalable, distributed revision control system with an
18 unusually rich command set that provides both high-level operations and
19 full access to internals.
20 See gittutorial(7) to get started, then see Everyday Git[1] for a
22 useful minimum set of commands, and "man git-commandname" for
23 documentation of each command. CVS users may also want to read gitcvs-
24 migration(7). See the Git User’s Manual[2] for a more in-depth
25 introduction.
26 The <command> is either a name of a Git command (see below) or an alias
28 as defined in the configuration file (see git-config(1)).
29 Formatted and hyperlinked version of the latest git documentation can
31 be viewed at http://www.kernel.org/pub/software/scm/git/docs/.
32
34 --version
35 Prints the git suite version that the git program came from.
36 --help
38 Prints the synopsis and a list of the most commonly used commands.
39 If the option --all or -a is given then all available commands are
40 printed. If a git command is named this option will bring up the
41 manual page for that command.
42 Other options are available to control how the manual page is
44 displayed. See git-help(1) for more information, because git --help
45 ... is converted internally into git help ....
46 -c <name>=<value>
48 Pass a configuration parameter to the command. The value given will
49 override values from configuration files. The <name> is expected in
50 the same format as listed by git config (subkeys separated by
51 dots).
52 --exec-path[=<path>]
54 Path to wherever your core git programs are installed. This can
55 also be controlled by setting the GIT_EXEC_PATH environment
56 variable. If no path is given, git will print the current setting
57 and then exit.
58 --html-path
60 Print the path to wherever your git HTML documentation is installed
61 and exit.
62 -p, --paginate
64 Pipe all output into less (or if set, $PAGER) if standard output is
65 a terminal. This overrides the pager.<cmd> configuration options
66 (see the "Configuration Mechanism" section below).
67 --no-pager
69 Do not pipe git output into a pager.
70 --git-dir=<path>
72 Set the path to the repository. This can also be controlled by
73 setting the GIT_DIR environment variable. It can be an absolute
74 path or relative path to current working directory.
75 --work-tree=<path>
77 Set the path to the working tree. It can be an absolute path or a
78 path relative to the current working directory. This can also be
79 controlled by setting the GIT_WORK_TREE environment variable and
80 the core.worktree configuration variable (see core.worktree in git-
81 config(1) for a more detailed discussion).
82 --bare
84 Treat the repository as a bare repository. If GIT_DIR environment
85 is not set, it is set to the current working directory.
86 --no-replace-objects
88 Do not use replacement refs to replace git objects. See git-
89 replace(1) for more information.
90
92 See the references above to get started using git. The following is
93 probably more detail than necessary for a first-time user.
94 The git concepts chapter of the user-manual[3] and gitcore-tutorial(7)
96 both provide introductions to the underlying git architecture.
97 See gitworkflows(7) for an overview of recommended workflows.
99 See also the howto[4] documents for some useful examples.
101 The internals are documented in the GIT API documentation[5].
103
105 We divide git into high level ("porcelain") commands and low level
106 ("plumbing") commands.
107
109 We separate the porcelain commands into the main commands and some
110 ancillary user utilities.
111 Main porcelain commands
113 git-add(1)
114 Add file contents to the index.
115 git-am(1)
117 Apply a series of patches from a mailbox.
118 git-archive(1)
120 Create an archive of files from a named tree.
121 git-bisect(1)
123 Find by binary search the change that introduced a bug.
124 git-branch(1)
126 List, create, or delete branches.
127 git-bundle(1)
129 Move objects and refs by archive.
130 git-checkout(1)
132 Checkout a branch or paths to the working tree.
133 git-cherry-pick(1)
135 Apply the changes introduced by some existing commits.
136 git-citool(1)
138 Graphical alternative to git-commit.
139 git-clean(1)
141 Remove untracked files from the working tree.
142 git-clone(1)
144 Clone a repository into a new directory.
145 git-commit(1)
147 Record changes to the repository.
148 git-describe(1)
150 Show the most recent tag that is reachable from a commit.
151 git-diff(1)
153 Show changes between commits, commit and working tree, etc.
154 git-fetch(1)
156 Download objects and refs from another repository.
157 git-format-patch(1)
159 Prepare patches for e-mail submission.
160 git-gc(1)
162 Cleanup unnecessary files and optimize the local repository.
163 git-grep(1)
165 Print lines matching a pattern.
166 git-gui(1)
168 A portable graphical interface to Git.
169 git-init(1)
171 Create an empty git repository or reinitialize an existing one.
172 git-log(1)
174 Show commit logs.
175 git-merge(1)
177 Join two or more development histories together.
178 git-mv(1)
180 Move or rename a file, a directory, or a symlink.
181 git-notes(1)
183 Add or inspect object notes.
184 git-pull(1)
186 Fetch from and merge with another repository or a local branch.
187 git-push(1)
189 Update remote refs along with associated objects.
190 git-rebase(1)
192 Forward-port local commits to the updated upstream head.
193 git-reset(1)
195 Reset current HEAD to the specified state.
196 git-revert(1)
198 Revert some existing commits.
199 git-rm(1)
201 Remove files from the working tree and from the index.
202 git-shortlog(1)
204 Summarize git log output.
205 git-show(1)
207 Show various types of objects.
208 git-stash(1)
210 Stash the changes in a dirty working directory away.
211 git-status(1)
213 Show the working tree status.
214 git-submodule(1)
216 Initialize, update or inspect submodules.
217 git-tag(1)
219 Create, list, delete or verify a tag object signed with GPG.
220 gitk(1)
222 The git repository browser.
223 Ancillary Commands
225 Manipulators:
226 git-config(1)
228 Get and set repository or global options.
229 git-fast-export(1)
231 Git data exporter.
232 git-fast-import(1)
234 Backend for fast Git data importers.
235 git-filter-branch(1)
237 Rewrite branches.
238 git-lost-found(1)
240 (deprecated) Recover lost refs that luckily have not yet been
241 pruned.
242 git-mergetool(1)
244 Run merge conflict resolution tools to resolve merge conflicts.
245 git-pack-refs(1)
247 Pack heads and tags for efficient repository access.
248 git-prune(1)
250 Prune all unreachable objects from the object database.
251 git-reflog(1)
253 Manage reflog information.
254 git-relink(1)
256 Hardlink common objects in local repositories.
257 git-remote(1)
259 manage set of tracked repositories.
260 git-repack(1)
262 Pack unpacked objects in a repository.
263 git-replace(1)
265 Create, list, delete refs to replace objects.
266 git-repo-config(1)
268 (deprecated) Get and set repository or global options.
269 Interrogators:
271 git-annotate(1)
273 Annotate file lines with commit information.
274 git-blame(1)
276 Show what revision and author last modified each line of a file.
277 git-cherry(1)
279 Find commits not merged upstream.
280 git-count-objects(1)
282 Count unpacked number of objects and their disk consumption.
283 git-difftool(1)
285 Show changes using common diff tools.
286 git-fsck(1)
288 Verifies the connectivity and validity of the objects in the
289 database.
290 git-get-tar-commit-id(1)
292 Extract commit ID from an archive created using git-archive.
293 git-help(1)
295 display help information about git.
296 git-instaweb(1)
298 Instantly browse your working repository in gitweb.
299 git-merge-tree(1)
301 Show three-way merge without touching index.
302 git-rerere(1)
304 Reuse recorded resolution of conflicted merges.
305 git-rev-parse(1)
307 Pick out and massage parameters.
308 git-show-branch(1)
310 Show branches and their commits.
311 git-verify-tag(1)
313 Check the GPG signature of tags.
314 git-whatchanged(1)
316 Show logs with difference each commit introduces.
317 Interacting with Others
319 These commands are to interact with foreign SCM and with other people
320 via patch over e-mail.
321 git-archimport(1)
323 Import an Arch repository into git.
324 git-cvsexportcommit(1)
326 Export a single commit to a CVS checkout.
327 git-cvsimport(1)
329 Salvage your data out of another SCM people love to hate.
330 git-cvsserver(1)
332 A CVS server emulator for git.
333 git-imap-send(1)
335 Send a collection of patches from stdin to an IMAP folder.
336 git-quiltimport(1)
338 Applies a quilt patchset onto the current branch.
339 git-request-pull(1)
341 Generates a summary of pending changes.
342 git-send-email(1)
344 Send a collection of patches as emails.
345 git-svn(1)
347 Bidirectional operation between a Subversion repository and git.
348
350 Although git includes its own porcelain layer, its low-level commands
351 are sufficient to support development of alternative porcelains.
352 Developers of such porcelains might start by reading about git-update-
353 index(1) and git-read-tree(1).
354 The interface (input, output, set of options and the semantics) to
356 these low-level commands are meant to be a lot more stable than
357 Porcelain level commands, because these commands are primarily for
358 scripted use. The interface to Porcelain commands on the other hand are
359 subject to change in order to improve the end user experience.
360 The following description divides the low-level commands into commands
362 that manipulate objects (in the repository, index, and working tree),
363 commands that interrogate and compare objects, and commands that move
364 objects and references between repositories.
365 Manipulation commands
367 git-apply(1)
368 Apply a patch to files and/or to the index.
369 git-checkout-index(1)
371 Copy files from the index to the working tree.
372 git-commit-tree(1)
374 Create a new commit object.
375 git-hash-object(1)
377 Compute object ID and optionally creates a blob from a file.
378 git-index-pack(1)
380 Build pack index file for an existing packed archive.
381 git-merge-file(1)
383 Run a three-way file merge.
384 git-merge-index(1)
386 Run a merge for files needing merging.
387 git-mktag(1)
389 Creates a tag object.
390 git-mktree(1)
392 Build a tree-object from ls-tree formatted text.
393 git-pack-objects(1)
395 Create a packed archive of objects.
396 git-prune-packed(1)
398 Remove extra objects that are already in pack files.
399 git-read-tree(1)
401 Reads tree information into the index.
402 git-symbolic-ref(1)
404 Read and modify symbolic refs.
405 git-unpack-objects(1)
407 Unpack objects from a packed archive.
408 git-update-index(1)
410 Register file contents in the working tree to the index.
411 git-update-ref(1)
413 Update the object name stored in a ref safely.
414 git-write-tree(1)
416 Create a tree object from the current index.
417 Interrogation commands
419 git-cat-file(1)
420 Provide content or type and size information for repository
421 objects.
422 git-diff-files(1)
424 Compares files in the working tree and the index.
425 git-diff-index(1)
427 Compares content and mode of blobs between the index and
428 repository.
429 git-diff-tree(1)
431 Compares the content and mode of blobs found via two tree objects.
432 git-for-each-ref(1)
434 Output information on each ref.
435 git-ls-files(1)
437 Show information about files in the index and the working tree.
438 git-ls-remote(1)
440 List references in a remote repository.
441 git-ls-tree(1)
443 List the contents of a tree object.
444 git-merge-base(1)
446 Find as good common ancestors as possible for a merge.
447 git-name-rev(1)
449 Find symbolic names for given revs.
450 git-pack-redundant(1)
452 Find redundant pack files.
453 git-rev-list(1)
455 Lists commit objects in reverse chronological order.
456 git-show-index(1)
458 Show packed archive index.
459 git-show-ref(1)
461 List references in a local repository.
462 git-tar-tree(1)
464 (deprecated) Create a tar archive of the files in the named tree
465 object.
466 git-unpack-file(1)
468 Creates a temporary file with a blob’s contents.
469 git-var(1)
471 Show a git logical variable.
472 git-verify-pack(1)
474 Validate packed git archive files.
475 In general, the interrogate commands do not touch the files in the
477 working tree.
478 Synching repositories
480 git-daemon(1)
481 A really simple server for git repositories.
482 git-fetch-pack(1)
484 Receive missing objects from another repository.
485 git-http-backend(1)
487 Server side implementation of Git over HTTP.
488 git-send-pack(1)
490 Push objects over git protocol to another repository.
491 git-update-server-info(1)
493 Update auxiliary info file to help dumb servers.
494 The following are helper commands used by the above; end users
496 typically do not use them directly.
497 git-http-fetch(1)
499 Download from a remote git repository via HTTP.
500 git-http-push(1)
502 Push objects over HTTP/DAV to another repository.
503 git-parse-remote(1)
505 Routines to help parsing remote repository access parameters.
506 git-receive-pack(1)
508 Receive what is pushed into the repository.
509 git-shell(1)
511 Restricted login shell for Git-only SSH access.
512 git-upload-archive(1)
514 Send archive back to git-archive.
515 git-upload-pack(1)
517 Send objects packed back to git-fetch-pack.
518 Internal helper commands
520 These are internal helper commands used by other commands; end users
521 typically do not use them directly.
522 git-check-attr(1)
524 Display gitattributes information.
525 git-check-ref-format(1)
527 Ensures that a reference name is well formed.
528 git-fmt-merge-msg(1)
530 Produce a merge commit message.
531 git-mailinfo(1)
533 Extracts patch and authorship from a single e-mail message.
534 git-mailsplit(1)
536 Simple UNIX mbox splitter program.
537 git-merge-one-file(1)
539 The standard helper program to use with git-merge-index.
540 git-patch-id(1)
542 Compute unique ID for a patch.
543 git-peek-remote(1)
545 (deprecated) List the references in a remote repository.
546 git-sh-setup(1)
548 Common git shell script setup code.
549 git-stripspace(1)
551 Filter out empty lines.
552
554 Starting from 0.99.9 (actually mid 0.99.8.GIT), .git/config file is
555 used to hold per-repository configuration options. It is a simple text
556 file modeled after .ini format familiar to some people. Here is an
557 example:
558 #
560 # A '#' or ';' character indicates a comment.
561 #
562 ; core variables
564 [core]
565 ; Don't trust file modes
566 filemode = false
567 ; user identity
569 [user]
570 name = "Junio C Hamano"
571 email = "junkio@twinsun.com"
572 Various commands read from the configuration file and adjust their
575 operation accordingly. See git-config(1) for a list.
576
578 <object>
579 Indicates the object name for any type of object.
580 <blob>
582 Indicates a blob object name.
583 <tree>
585 Indicates a tree object name.
586 <commit>
588 Indicates a commit object name.
589 <tree-ish>
591 Indicates a tree, commit or tag object name. A command that takes a
592 <tree-ish> argument ultimately wants to operate on a <tree> object
593 but automatically dereferences <commit> and <tag> objects that
594 point at a <tree>.
595 <commit-ish>
597 Indicates a commit or tag object name. A command that takes a
598 <commit-ish> argument ultimately wants to operate on a <commit>
599 object but automatically dereferences <tag> objects that point at a
600 <commit>.
601 <type>
603 Indicates that an object type is required. Currently one of: blob,
604 tree, commit, or tag.
605 <file>
607 Indicates a filename - almost always relative to the root of the
608 tree structure GIT_INDEX_FILE describes.
609
611 Any git command accepting any <object> can also use the following
612 symbolic notation:
613 HEAD
615 indicates the head of the current branch (i.e. the contents of
616 $GIT_DIR/HEAD).
617 <tag>
619 a valid tag name (i.e. the contents of $GIT_DIR/refs/tags/<tag>).
620 <head>
622 a valid head name (i.e. the contents of
623 $GIT_DIR/refs/heads/<head>).
624 For a more complete list of ways to spell object names, see "SPECIFYING
626 REVISIONS" section in gitrevisions(7).
627
629 Please see the gitrepository-layout(5) document.
630 Read githooks(5) for more details about each hook.
632 Higher level SCMs may provide and manage additional information in the
634 $GIT_DIR.
635
637 Please see gitglossary(7).
638
640 Various git commands use the following environment variables:
641 The git Repository
643 These environment variables apply to all core git commands. Nb: it is
644 worth noting that they may be used/overridden by SCMS sitting above git
645 so take care if using Cogito etc.
646 GIT_INDEX_FILE
648 This environment allows the specification of an alternate index
649 file. If not specified, the default of $GIT_DIR/index is used.
650 GIT_OBJECT_DIRECTORY
652 If the object storage directory is specified via this environment
653 variable then the sha1 directories are created underneath -
654 otherwise the default $GIT_DIR/objects directory is used.
655 GIT_ALTERNATE_OBJECT_DIRECTORIES
657 Due to the immutable nature of git objects, old objects can be
658 archived into shared, read-only directories. This variable
659 specifies a ":" separated (on Windows ";" separated) list of git
660 object directories which can be used to search for git objects. New
661 objects will not be written to these directories.
662 GIT_DIR
664 If the GIT_DIR environment variable is set then it specifies a path
665 to use instead of the default .git for the base of the repository.
666 GIT_WORK_TREE
668 Set the path to the working tree. The value will not be used in
669 combination with repositories found automatically in a .git
670 directory (i.e. $GIT_DIR is not set). This can also be controlled
671 by the --work-tree command line option and the core.worktree
672 configuration variable.
673 GIT_CEILING_DIRECTORIES
675 This should be a colon-separated list of absolute paths. If set, it
676 is a list of directories that git should not chdir up into while
677 looking for a repository directory. It will not exclude the current
678 working directory or a GIT_DIR set on the command line or in the
679 environment. (Useful for excluding slow-loading network
680 directories.)
681 GIT_DISCOVERY_ACROSS_FILESYSTEM
683 When run in a directory that does not have ".git" repository
684 directory, git tries to find such a directory in the parent
685 directories to find the top of the working tree, but by default it
686 does not cross filesystem boundaries. This environment variable can
687 be set to true to tell git not to stop at filesystem boundaries.
688 Like GIT_CEILING_DIRECTORIES, this will not affect an explicit
689 repository directory set via GIT_DIR or on the command line.
690 git Commits
692 GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME,
693 GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, EMAIL
694 see git-commit-tree(1)
695 git Diffs
697 GIT_DIFF_OPTS
698 Only valid setting is "--unified=??" or "-u??" to set the number of
699 context lines shown when a unified diff is created. This takes
700 precedence over any "-U" or "--unified" option value passed on the
701 git diff command line.
702 GIT_EXTERNAL_DIFF
704 When the environment variable GIT_EXTERNAL_DIFF is set, the program
705 named by it is called, instead of the diff invocation described
706 above. For a path that is added, removed, or modified,
707 GIT_EXTERNAL_DIFF is called with 7 parameters:
708 path old-file old-hex old-mode new-file new-hex new-mode
710 where:
712 <old|new>-file
714 are files GIT_EXTERNAL_DIFF can use to read the contents of
715 <old|new>,
716 <old|new>-hex
718 are the 40-hexdigit SHA1 hashes,
719 <old|new>-mode
721 are the octal representation of the file modes.
722 + The file parameters can point at the user’s working file (e.g.
724 new-file in "git-diff-files"), /dev/null (e.g. old-file when a new file
725 is added), or a temporary file (e.g. old-file in the index).
726 GIT_EXTERNAL_DIFF should not worry about unlinking the temporary file
727 --- it is removed when GIT_EXTERNAL_DIFF exits.
728 + For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1
730 parameter, <path>.
731 other
733 GIT_MERGE_VERBOSITY
734 A number controlling the amount of output shown by the recursive
735 merge strategy. Overrides merge.verbosity. See git-merge(1)
736 GIT_PAGER
738 This environment variable overrides $PAGER. If it is set to an
739 empty string or to the value "cat", git will not launch a pager.
740 See also the core.pager option in git-config(1).
741 GIT_SSH
743 If this environment variable is set then git fetch and git push
744 will use this command instead of ssh when they need to connect to a
745 remote system. The $GIT_SSH command will be given exactly two
746 arguments: the username@host (or just host) from the URL and the
747 shell command to execute on that remote system.
748 To pass options to the program that you want to list in GIT_SSH you
750 will need to wrap the program and options into a shell script, then
751 set GIT_SSH to refer to the shell script.
752 Usually it is easier to configure any desired options through your
754 personal .ssh/config file. Please consult your ssh documentation
755 for further details.
756 GIT_ASKPASS
758 If this environment variable is set, then git commands which need
759 to acquire passwords or passphrases (e.g. for HTTP or IMAP
760 authentication) will call this program with a suitable prompt as
761 command line argument and read the password from its STDOUT. See
762 also the core.askpass option in git-config(1).
763 GIT_FLUSH
765 If this environment variable is set to "1", then commands such as
766 git blame (in incremental mode), git rev-list, git log, and git
767 whatchanged will force a flush of the output stream after each
768 commit-oriented record have been flushed. If this variable is set
769 to "0", the output of these commands will be done using completely
770 buffered I/O. If this environment variable is not set, git will
771 choose buffered or record-oriented flushing based on whether stdout
772 appears to be redirected to a file or not.
773 GIT_TRACE
775 If this variable is set to "1", "2" or "true" (comparison is case
776 insensitive), git will print trace: messages on stderr telling
777 about alias expansion, built-in command execution and external
778 command execution. If this variable is set to an integer value
779 greater than 1 and lower than 10 (strictly) then git will interpret
780 this value as an open file descriptor and will try to write the
781 trace messages into this file descriptor. Alternatively, if this
782 variable is set to an absolute path (starting with a / character),
783 git will interpret this as a file path and will try to write the
784 trace messages into it.
785
787 More detail on the following is available from the git concepts chapter
788 of the user-manual[3] and gitcore-tutorial(7).
789 A git project normally consists of a working directory with a ".git"
791 subdirectory at the top level. The .git directory contains, among other
792 things, a compressed object database representing the complete history
793 of the project, an "index" file which links that history to the current
794 contents of the working tree, and named pointers into that history such
795 as tags and branch heads.
796 The object database contains objects of three main types: blobs, which
798 hold file data; trees, which point to blobs and other trees to build up
799 directory hierarchies; and commits, which each reference a single tree
800 and some number of parent commits.
801 The commit, equivalent to what other systems call a "changeset" or
803 "version", represents a step in the project’s history, and each parent
804 represents an immediately preceding step. Commits with more than one
805 parent represent merges of independent lines of development.
806 All objects are named by the SHA1 hash of their contents, normally
808 written as a string of 40 hex digits. Such names are globally unique.
809 The entire history leading up to a commit can be vouched for by signing
810 just that commit. A fourth object type, the tag, is provided for this
811 purpose.
812 When first created, objects are stored in individual files, but for
814 efficiency may later be compressed together into "pack files".
815 Named pointers called refs mark interesting points in history. A ref
817 may contain the SHA1 name of an object or the name of another ref. Refs
818 with names beginning ref/head/ contain the SHA1 name of the most recent
819 commit (or "head") of a branch under development. SHA1 names of tags of
820 interest are stored under ref/tags/. A special ref named HEAD contains
821 the name of the currently checked-out branch.
822 The index file is initialized with a list of all paths and, for each
824 path, a blob object and a set of attributes. The blob object represents
825 the contents of the file as of the head of the current branch. The
826 attributes (last modified time, size, etc.) are taken from the
827 corresponding file in the working tree. Subsequent changes to the
828 working tree can be found by comparing these attributes. The index may
829 be updated with new content, and new commits may be created from the
830 content stored in the index.
831 The index is also capable of storing multiple entries (called "stages")
833 for a given pathname. These stages are used to hold the various
834 unmerged version of a file when a merge is in progress.
835
837 · git’s founding father is Linus Torvalds <torvalds@osdl.org[6]>.
838 · The current git nurse is Junio C Hamano <gitster@pobox.com[7]>.
840 · The git potty was written by Andreas Ericsson <ae@op5.se[8]>.
842 · General upbringing is handled by the git-list
844 <git@vger.kernel.org[9]>.
845
847 The documentation for git suite was started by David Greaves
848 <david@dgreaves.com[10]>, and later enhanced greatly by the
849 contributors on the git-list <git@vger.kernel.org[9]>.
850
852 Report bugs to the Git mailing list <git@vger.kernel.org[9]> where the
853 development and maintenance is primarily done. You do not have to be
854 subscribed to the list to send a message there.
855
857 gittutorial(7), gittutorial-2(7), Everyday Git[1], gitcvs-migration(7),
858 gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User’s
859 Manual[2], gitworkflows(7)
860
862 Part of the git(1) suite
863
865 1. Everyday Git
866 file:///usr/share/doc/git-1.7.4.4/everyday.html
867 2. Git User’s Manual
869 file:///usr/share/doc/git-1.7.4.4/user-manual.html
870 3. git concepts chapter of the user-manual
872 file:///usr/share/doc/git-1.7.4.4/user-manual.html#git-concepts
873 4. howto
875 file:///usr/share/doc/git-1.7.4.4/howto-index.html
876 5. GIT API documentation
878 file:///usr/share/doc/git-1.7.4.4/technical/api-index.html
879 6. torvalds@osdl.org
881 mailto:torvalds@osdl.org
882 7. gitster@pobox.com
884 mailto:gitster@pobox.com
885 8. ae@op5.se
887 mailto:ae@op5.se
888 9. git@vger.kernel.org
890 mailto:git@vger.kernel.org
891 10. david@dgreaves.com
893 mailto:david@dgreaves.com
894Git 1.7.4.4 04/11/2011 GIT(1)