6 git - the stupid content tracker
12 'git' [--version] [--exec-path[=GIT_EXEC_PATH]] [-p|--paginate]
13 [--bare] [--git-dir=GIT_DIR] [--help] COMMAND [ARGS]
17 Git is a fast, scalable, distributed revision control system with an
18 unusually rich command set that provides both high-level operations
19 and full access to internals.
21 See this link:tutorial.html[tutorial] to get started, then see
22 link:everyday.html[Everyday Git] for a useful minimum set of commands, and
23 "man git-commandname" for documentation of each command. CVS users may
24 also want to read link:cvs-migration.html[CVS migration].
26 The COMMAND is either a name of a Git command (see below) or an alias
27 as defined in the configuration file (see gitlink:git-repo-config[1]).
32 Prints the git suite version that the 'git' program came from.
35 Prints the synopsis and a list of the most commonly used
36 commands. If a git command is named this option will bring up
37 the man-page for that command. If the option '--all' or '-a' is
38 given then all available commands are printed.
41 Path to wherever your core git programs are installed.
42 This can also be controlled by setting the GIT_EXEC_PATH
43 environment variable. If no path is given 'git' will print
44 the current setting and then exit.
47 Pipe all output into 'less' (or if set, $PAGER).
50 Set the path to the repository. This can also be controlled by
51 setting the GIT_DIR environment variable.
54 Same as --git-dir=`pwd`.
59 See the references above to get started using git. The following is
60 probably more detail than necessary for a first-time user.
62 The <<Discussion,Discussion>> section below and the
63 link:core-tutorial.html[Core tutorial] both provide introductions to the
64 underlying git architecture.
66 See also the link:howto-index.html[howto] documents for some useful
72 We divide git into high level ("porcelain") commands and low level
73 ("plumbing") commands.
75 Low-level commands (plumbing)
76 -----------------------------
78 Although git includes its
79 own porcelain layer, its low-level commands are sufficient to support
80 development of alternative porcelains. Developers of such porcelains
81 might start by reading about gitlink:git-update-index[1] and
82 gitlink:git-read-tree[1].
84 We divide the low-level commands into commands that manipulate objects (in
85 the repository, index, and working tree), commands that interrogate and
86 compare objects, and commands that move objects and references between
91 gitlink:git-apply[1]::
92 Reads a "diff -up1" or git generated patch file and
93 applies it to the working tree.
95 gitlink:git-checkout-index[1]::
96 Copy files from the index to the working tree.
98 gitlink:git-commit-tree[1]::
99 Creates a new commit object.
101 gitlink:git-hash-object[1]::
102 Computes the object ID from a file.
104 gitlink:git-index-pack[1]::
105 Build pack idx file for an existing packed archive.
107 gitlink:git-init-db[1]::
108 Creates an empty git object database, or reinitialize an
111 gitlink:git-merge-index[1]::
112 Runs a merge for files needing merging.
114 gitlink:git-mktag[1]::
115 Creates a tag object.
117 gitlink:git-mktree[1]::
118 Build a tree-object from ls-tree formatted text.
120 gitlink:git-pack-objects[1]::
121 Creates a packed archive of objects.
123 gitlink:git-prune-packed[1]::
124 Remove extra objects that are already in pack files.
126 gitlink:git-read-tree[1]::
127 Reads tree information into the index.
129 gitlink:git-repo-config[1]::
130 Get and set options in .git/config.
132 gitlink:git-unpack-objects[1]::
133 Unpacks objects out of a packed archive.
135 gitlink:git-update-index[1]::
136 Registers files in the working tree to the index.
138 gitlink:git-write-tree[1]::
139 Creates a tree from the index.
142 Interrogation commands
143 ~~~~~~~~~~~~~~~~~~~~~~
145 gitlink:git-cat-file[1]::
146 Provide content or type/size information for repository objects.
148 gitlink:git-describe[1]::
149 Show the most recent tag that is reachable from a commit.
151 gitlink:git-diff-index[1]::
152 Compares content and mode of blobs between the index and repository.
154 gitlink:git-diff-files[1]::
155 Compares files in the working tree and the index.
157 gitlink:git-diff-stages[1]::
158 Compares two "merge stages" in the index.
160 gitlink:git-diff-tree[1]::
161 Compares the content and mode of blobs found via two tree objects.
163 gitlink:git-fsck-objects[1]::
164 Verifies the connectivity and validity of the objects in the database.
166 gitlink:git-ls-files[1]::
167 Information about files in the index and the working tree.
169 gitlink:git-ls-tree[1]::
170 Displays a tree object in human readable form.
172 gitlink:git-merge-base[1]::
173 Finds as good common ancestors as possible for a merge.
175 gitlink:git-name-rev[1]::
176 Find symbolic names for given revs.
178 gitlink:git-pack-redundant[1]::
179 Find redundant pack files.
181 gitlink:git-rev-list[1]::
182 Lists commit objects in reverse chronological order.
184 gitlink:git-show-index[1]::
185 Displays contents of a pack idx file.
187 gitlink:git-tar-tree[1]::
188 Creates a tar archive of the files in the named tree object.
190 gitlink:git-unpack-file[1]::
191 Creates a temporary file with a blob's contents.
194 Displays a git logical variable.
196 gitlink:git-verify-pack[1]::
197 Validates packed git archive files.
199 In general, the interrogate commands do not touch the files in
203 Synching repositories
204 ~~~~~~~~~~~~~~~~~~~~~
206 gitlink:git-fetch-pack[1]::
207 Updates from a remote repository (engine for ssh and
210 gitlink:git-http-fetch[1]::
211 Downloads a remote git repository via HTTP by walking
214 gitlink:git-local-fetch[1]::
215 Duplicates another git repository on a local system by
216 walking commit chain.
218 gitlink:git-peek-remote[1]::
219 Lists references on a remote repository using
220 upload-pack protocol (engine for ssh and local
223 gitlink:git-receive-pack[1]::
224 Invoked by 'git-send-pack' to receive what is pushed to it.
226 gitlink:git-send-pack[1]::
227 Pushes to a remote repository, intelligently.
229 gitlink:git-http-push[1]::
230 Push missing objects using HTTP/DAV.
232 gitlink:git-shell[1]::
233 Restricted shell for GIT-only SSH access.
235 gitlink:git-ssh-fetch[1]::
236 Pulls from a remote repository over ssh connection by
237 walking commit chain.
239 gitlink:git-ssh-upload[1]::
240 Helper "server-side" program used by git-ssh-fetch.
242 gitlink:git-update-server-info[1]::
243 Updates auxiliary information on a dumb server to help
244 clients discover references and packs on it.
246 gitlink:git-upload-archive[1]::
247 Invoked by 'git-archive' to send a generated archive.
249 gitlink:git-upload-pack[1]::
250 Invoked by 'git-fetch-pack' to push
254 High-level commands (porcelain)
255 -------------------------------
257 We separate the porcelain commands into the main commands and some
258 ancillary user utilities.
260 Main porcelain commands
261 ~~~~~~~~~~~~~~~~~~~~~~~
264 Add paths to the index.
267 Apply patches from a mailbox, but cooler.
269 gitlink:git-applymbox[1]::
270 Apply patches from a mailbox, original version by Linus.
272 gitlink:git-archive[1]::
273 Creates an archive of files from a named tree.
275 gitlink:git-bisect[1]::
276 Find the change that introduced a bug by binary search.
278 gitlink:git-branch[1]::
279 Create and Show branches.
281 gitlink:git-checkout[1]::
282 Checkout and switch to a branch.
284 gitlink:git-cherry-pick[1]::
285 Cherry-pick the effect of an existing commit.
287 gitlink:git-clean[1]::
288 Remove untracked files from the working tree.
290 gitlink:git-clone[1]::
291 Clones a repository into a new directory.
293 gitlink:git-commit[1]::
294 Record changes to the repository.
296 gitlink:git-diff[1]::
297 Show changes between commits, commit and working tree, etc.
299 gitlink:git-fetch[1]::
300 Download from a remote repository via various protocols.
302 gitlink:git-format-patch[1]::
303 Prepare patches for e-mail submission.
305 gitlink:git-grep[1]::
306 Print lines matching a pattern.
309 The git repository browser.
314 gitlink:git-ls-remote[1]::
315 Shows references in a remote or local repository.
317 gitlink:git-merge[1]::
318 Grand unified merge driver.
321 Move or rename a file, a directory, or a symlink.
323 gitlink:git-pull[1]::
324 Fetch from and merge with a remote repository.
326 gitlink:git-push[1]::
327 Update remote refs along with associated objects.
329 gitlink:git-rebase[1]::
330 Rebase local commits to the updated upstream head.
332 gitlink:git-repack[1]::
333 Pack unpacked objects in a repository.
335 gitlink:git-rerere[1]::
336 Reuse recorded resolution of conflicted merges.
338 gitlink:git-reset[1]::
339 Reset current HEAD to the specified state.
341 gitlink:git-resolve[1]::
344 gitlink:git-revert[1]::
345 Revert an existing commit.
348 Remove files from the working tree and from the index.
350 gitlink:git-shortlog[1]::
351 Summarizes 'git log' output.
353 gitlink:git-show[1]::
354 Show one commit log and its diff.
356 gitlink:git-show-branch[1]::
357 Show branches and their commits.
359 gitlink:git-status[1]::
360 Shows the working tree status.
362 gitlink:git-verify-tag[1]::
363 Check the GPG signature of tag.
365 gitlink:git-whatchanged[1]::
366 Shows commit logs and differences they introduce.
373 gitlink:git-applypatch[1]::
374 Apply one patch extracted from an e-mail.
376 gitlink:git-archimport[1]::
377 Import an arch repository into git.
379 gitlink:git-convert-objects[1]::
380 Converts old-style git repository.
382 gitlink:git-cvsimport[1]::
383 Salvage your data out of another SCM people love to hate.
385 gitlink:git-cvsexportcommit[1]::
386 Export a single commit to a CVS checkout.
388 gitlink:git-cvsserver[1]::
389 A CVS server emulator for git.
391 gitlink:git-lost-found[1]::
392 Recover lost refs that luckily have not yet been pruned.
394 gitlink:git-merge-one-file[1]::
395 The standard helper program to use with `git-merge-index`.
397 gitlink:git-prune[1]::
398 Prunes all unreachable objects from the object database.
400 gitlink:git-quiltimport[1]::
401 Applies a quilt patchset onto the current branch.
403 gitlink:git-relink[1]::
404 Hardlink common objects in local repositories.
407 Bidirectional operation between a single Subversion branch and git.
409 gitlink:git-svnimport[1]::
410 Import a SVN repository into git.
412 gitlink:git-sh-setup[1]::
413 Common git shell script setup code.
415 gitlink:git-symbolic-ref[1]::
416 Read and modify symbolic refs.
419 An example script to create a tag object signed with GPG.
421 gitlink:git-update-ref[1]::
422 Update the object name stored in a ref safely.
427 gitlink:git-annotate[1]::
428 Annotate file lines with commit info.
430 gitlink:git-blame[1]::
431 Blame file lines on commits.
433 gitlink:git-check-ref-format[1]::
434 Make sure ref name is well formed.
436 gitlink:git-cherry[1]::
437 Find commits not merged upstream.
439 gitlink:git-count-objects[1]::
440 Count unpacked number of objects and their disk consumption.
442 gitlink:git-daemon[1]::
443 A really simple server for git repositories.
445 gitlink:git-fmt-merge-msg[1]::
446 Produce a merge commit message.
448 gitlink:git-get-tar-commit-id[1]::
449 Extract commit ID from an archive created using git-tar-tree.
451 gitlink:git-imap-send[1]::
452 Dump a mailbox from stdin into an imap folder.
454 gitlink:git-instaweb[1]::
455 Instantly browse your working repository in gitweb.
457 gitlink:git-mailinfo[1]::
458 Extracts patch and authorship information from a single
459 e-mail message, optionally transliterating the commit
462 gitlink:git-mailsplit[1]::
463 A stupid program to split UNIX mbox format mailbox into
464 individual pieces of e-mail.
466 gitlink:git-merge-tree[1]::
467 Show three-way merge without touching index.
469 gitlink:git-patch-id[1]::
470 Compute unique ID for a patch.
472 gitlink:git-parse-remote[1]::
473 Routines to help parsing `$GIT_DIR/remotes/` files.
475 gitlink:git-request-pull[1]::
478 gitlink:git-rev-parse[1]::
479 Pick out and massage parameters.
481 gitlink:git-send-email[1]::
482 Send patch e-mails out of "format-patch --mbox" output.
484 gitlink:git-symbolic-ref[1]::
485 Read and modify symbolic refs.
487 gitlink:git-stripspace[1]::
488 Filter out empty lines.
491 Configuration Mechanism
492 -----------------------
494 Starting from 0.99.9 (actually mid 0.99.8.GIT), `.git/config` file
495 is used to hold per-repository configuration options. It is a
496 simple text file modeled after `.ini` format familiar to some
497 people. Here is an example:
501 # A '#' or ';' character indicates a comment.
506 ; Don't trust file modes
511 name = "Junio C Hamano"
512 email = "junkio@twinsun.com"
516 Various commands read from the configuration file and adjust
517 their operation accordingly.
520 Identifier Terminology
521 ----------------------
523 Indicates the object name for any type of object.
526 Indicates a blob object name.
529 Indicates a tree object name.
532 Indicates a commit object name.
535 Indicates a tree, commit or tag object name. A
536 command that takes a <tree-ish> argument ultimately wants to
537 operate on a <tree> object but automatically dereferences
538 <commit> and <tag> objects that point at a <tree>.
541 Indicates that an object type is required.
542 Currently one of: `blob`, `tree`, `commit`, or `tag`.
545 Indicates a filename - almost always relative to the
546 root of the tree structure `GIT_INDEX_FILE` describes.
550 Any git command accepting any <object> can also use the following
554 indicates the head of the current branch (i.e. the
555 contents of `$GIT_DIR/HEAD`).
559 (i.e. the contents of `$GIT_DIR/refs/tags/<tag>`).
563 (i.e. the contents of `$GIT_DIR/refs/heads/<head>`).
565 For a more complete list of ways to spell object names, see
566 "SPECIFYING REVISIONS" section in gitlink:git-rev-parse[1].
569 File/Directory Structure
570 ------------------------
572 Please see link:repository-layout.html[repository layout] document.
574 Read link:hooks.html[hooks] for more details about each hook.
576 Higher level SCMs may provide and manage additional information in the
582 Please see link:glossary.html[glossary] document.
585 Environment Variables
586 ---------------------
587 Various git commands use the following environment variables:
591 These environment variables apply to 'all' core git commands. Nb: it
592 is worth noting that they may be used/overridden by SCMS sitting above
593 git so take care if using Cogito etc.
596 This environment allows the specification of an alternate
597 index file. If not specified, the default of `$GIT_DIR/index`
600 'GIT_OBJECT_DIRECTORY'::
601 If the object storage directory is specified via this
602 environment variable then the sha1 directories are created
603 underneath - otherwise the default `$GIT_DIR/objects`
606 'GIT_ALTERNATE_OBJECT_DIRECTORIES'::
607 Due to the immutable nature of git objects, old objects can be
608 archived into shared, read-only directories. This variable
609 specifies a ":" separated list of git object directories which
610 can be used to search for git objects. New objects will not be
611 written to these directories.
614 If the 'GIT_DIR' environment variable is set then it
615 specifies a path to use instead of the default `.git`
616 for the base of the repository.
623 'GIT_COMMITTER_NAME'::
624 'GIT_COMMITTER_EMAIL'::
625 see gitlink:git-commit-tree[1]
630 'GIT_EXTERNAL_DIFF'::
631 see the "generating patches" section in :
632 gitlink:git-diff-index[1];
633 gitlink:git-diff-files[1];
634 gitlink:git-diff-tree[1]
639 This environment variable overrides `$PAGER`.
642 If this variable is set to "1", "2" or "true" (comparison
643 is case insensitive), git will print `trace:` messages on
644 stderr telling about alias expansion, built-in command
645 execution and external command execution.
646 If this variable is set to an integer value greater than 1
647 and lower than 10 (strictly) then git will interpret this
648 value as an open file descriptor and will try to write the
649 trace messages into this file descriptor.
650 Alternatively, if this variable is set to an absolute path
651 (starting with a '/' character), git will interpret this
652 as a file path and will try to write the trace messages
655 Discussion[[Discussion]]
656 ------------------------
661 * git's founding father is Linus Torvalds <torvalds@osdl.org>.
662 * The current git nurse is Junio C Hamano <junkio@cox.net>.
663 * The git potty was written by Andres Ericsson <ae@op5.se>.
664 * General upbringing is handled by the git-list <git@vger.kernel.org>.
668 The documentation for git suite was started by David Greaves
669 <david@dgreaves.com>, and later enhanced greatly by the
670 contributors on the git-list <git@vger.kernel.org>.
674 Part of the gitlink:git[7] suite