.SH "DISCUSSION"
-The list of <file> given to the command is fed to git\-ls\-files command to list files that are not registerd in the index and are not ignored/excluded by $GIT_DIR/info/exclude file or \&.gitignore file in each directory\&. This means two things:
+The list of <file> given to the command is fed to git\-ls\-files command to list files that are not registered in the index and are not ignored/excluded by $GIT_DIR/info/exclude file or \&.gitignore file in each directory\&. This means two things:
.TP 3
1.
git-am \- Apply a series of patches in a mailbox
.SH "SYNOPSIS"
-
-git\-am [\-\-signoff] [\-\-dotest=<dir>] [\-\-utf8] [\-\-binary] [\-\-3way] <mbox>... git\-am [\-\-skip | \-\-resolved]
+.nf
+git\-am [\-\-signoff] [\-\-dotest=<dir>] [\-\-utf8] [\-\-binary] [\-\-3way] <mbox>...
+git\-am [\-\-skip | \-\-resolved]
+.fi
.SH "DESCRIPTION"
git-apply \- Apply patch on a git index file and a work tree
.SH "SYNOPSIS"
-
-git\-apply [\-\-stat] [\-\-numstat] [\-\-summary] [\-\-check] [\-\-index] [\-\-apply] [\-\-no\-add] [\-\-index\-info] [\-\-allow\-binary\-replacement] [\-z] [<patch>...]
+.nf
+git\-apply [\-\-stat] [\-\-numstat] [\-\-summary] [\-\-check] [\-\-index] [\-\-apply]
+ [\-\-no\-add] [\-\-index\-info] [\-\-allow\-binary\-replacement] [\-z]
+ [<patch>...]
+.fi
.SH "DESCRIPTION"
git-archimport \- Import an Arch repository into git
.SH "SYNOPSIS"
-
-git\-archimport [ \-h ] [ \-v ] [ \-o ] [ \-a ] [ \-f ] [ \-T ] [ \-D depth ] [ \-t tempdir ] <archive/branch> [ <archive/branch> ]
+.nf
+git\-archimport [\-h] [\-v] [\-o] [\-a] [\-f] [\-T] [\-D depth] [\-t tempdir]
+ <archive/branch> [ <archive/branch> ]
+.fi
.SH "DESCRIPTION"
-Imports a project from one or more Arch repositories\&. It will follow branches and repositories within the namespaces defined by the <archive/branch> parameters suppplied\&. If it cannot find the remote branch a merge comes from it will just import it as a regular commit\&. If it can find it, it will mark it as a merge whenever possible (see discussion below)\&.
+Imports a project from one or more Arch repositories\&. It will follow branches and repositories within the namespaces defined by the <archive/branch> parameters supplied\&. If it cannot find the remote branch a merge comes from it will just import it as a regular commit\&. If it can find it, it will mark it as a merge whenever possible (see discussion below)\&.
The script expects you to provide the key roots where it can start the import from an initial import or tag type of Arch commit\&. It will follow and import new branches within the provided roots\&.
.SH "SYNOPSIS"
-git\-cat\-file (\-t | \-s | \-e | <type>) <object>
+git\-cat\-file [\-t | \-s | \-e | <type>] <object>
.SH "DESCRIPTION"
git-checkout-index \- Copy files from the index to the working directory
.SH "SYNOPSIS"
-
-git\-checkout\-index [\-u] [\-q] [\-a] [\-f] [\-n] [\-\-prefix=<string>] [\-\-stage=<number>] [\-\-] <file>...
+.nf
+git\-checkout\-index [\-u] [\-q] [\-a] [\-f] [\-n] [\-\-prefix=<string>]
+ [\-\-stage=<number>] [\-\-] <file>...
+.fi
.SH "DESCRIPTION"
git-clone \- Clones a repository.
.SH "SYNOPSIS"
-
-git\-clone [\-l [\-s]] [\-q] [\-n] [\-o <name>] [\-u <upload\-pack>] <repository> [<directory>]
+.nf
+git\-clone [\-l [\-s]] [\-q] [\-n] [\-o <name>] [\-u <upload\-pack>]
+ <repository> [<directory>]
+.fi
.SH "DESCRIPTION"
(nb "<", ">" and "\\n"s are stripped)
-In \&.git/config file, the following items are used:
+In \&.git/config file, the following items are used for GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL:
.nf
[user]
git-commit \- Record your changes
.SH "SYNOPSIS"
-
-git\-commit [\-a] [\-s] [\-v] [(\-c | \-C) <commit> | \-F <file> | \-m <msg>] [\-e] [\-\-] <file>...
+.nf
+git\-commit [\-a] [\-s] [\-v] [(\-c | \-C) <commit> | \-F <file> | \-m <msg>]
+ [\-e] [\-\-] <file>...
+.fi
.SH "DESCRIPTION"
.SH "SYNOPSIS"
-git\-cvsexportcommmit\&.perl [ \-h ] [ \-v ] [ \-c ] [ \-p ] [PARENTCOMMIT] COMMITID
+git\-cvsexportcommmit [\-h] [\-v] [\-c] [\-p] [PARENTCOMMIT] COMMITID
.SH "DESCRIPTION"
git-cvsimport \- Import a CVS repository into git
.SH "SYNOPSIS"
-
-git\-cvsimport [ \-o <branch\-for\-HEAD> ] [ \-h ] [ \-v ] [ \-d <CVSROOT> ] [ \-p <options\-for\-cvsps> ] [ \-C <git_repository> ] [ \-i ] [ \-P <file> ] [ \-k ] [ \-s <subst> ] [ \-m ] [ \-M regex ] [ <CVS_module> ]
+.nf
+git\-cvsimport [\-o <branch\-for\-HEAD>] [\-h] [\-v] [\-d <CVSROOT>] [\-s <subst>]
+ [\-p <options\-for\-cvsps>] [\-C <git_repository>] [\-i] [\-P <file>]
+ [\-m] [\-M regex] [<CVS_module>]
+.fi
.SH "DESCRIPTION"
git-daemon \- A really simple server for git repositories.
.SH "SYNOPSIS"
-
-git\-daemon [\-\-verbose] [\-\-syslog] [\-\-inetd | \-\-port=n] [\-\-export\-all] [\-\-timeout=n] [\-\-init\-timeout=n] [\-\-strict\-paths] [directory...]
+.nf
+git\-daemon [\-\-verbose] [\-\-syslog] [\-\-inetd | \-\-port=n] [\-\-export\-all]
+ [\-\-timeout=n] [\-\-init\-timeout=n] [\-\-strict\-paths] [directory...]
+.fi
.SH "DESCRIPTION"
.TP
\-\-abbrev[=<n>]
-Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful dhexigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
+Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful hexdigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
.TP
\-B
.TP 3
1.
-It is preceeded with a "git diff" header, that looks like this:
+It is preceded with a "git diff" header, that looks like this:
.nf
.TP
\-\-abbrev[=<n>]
-Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful dhexigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
+Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful hexdigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
.TP
\-B
.TP 3
1.
-It is preceeded with a "git diff" header, that looks like this:
+It is preceded with a "git diff" header, that looks like this:
.nf
.fi
-For example, let's say that you have worked on your working directory, updated some files in the index and are ready to commit\&. You want to see eactly what you are going to commit is without having to write a new tree object and compare it that way, and to do that, you just do
+For example, let's say that you have worked on your working directory, updated some files in the index and are ready to commit\&. You want to see exactly what you are going to commit is without having to write a new tree object and compare it that way, and to do that, you just do
.nf
git\-diff\-index \-\-cached HEAD
.Sh "Note"
-As with other commands of this type, "git\-diff\-index" does not actually look at the contents of the file at all\&. So maybe kernel/sched\&.c hasn't actually changed, and it's just that you touched it\&. In either case, it's a note that you need to "git\-upate\-index" it to make the index be in sync\&.
+As with other commands of this type, "git\-diff\-index" does not actually look at the contents of the file at all\&. So maybe kernel/sched\&.c hasn't actually changed, and it's just that you touched it\&. In either case, it's a note that you need to "git\-update\-index" it to make the index be in sync\&.
.RE
.TP
\-\-abbrev[=<n>]
-Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful dhexigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
+Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful hexdigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
.TP
\-B
.TP 3
1.
-It is preceeded with a "git diff" header, that looks like this:
+It is preceded with a "git diff" header, that looks like this:
.nf
git-diff-tree \- Compares the content and mode of blobs found via two tree objects
.SH "SYNOPSIS"
-
-git\-diff\-tree [\-\-stdin] [\-m] [\-s] [\-v] [\-\-no\-commit\-id] [\-\-pretty] [\-t] [\-r] [\-\-root] [<common diff options>] <tree\-ish> [<tree\-ish>] [<path>...]
+.nf
+git\-diff\-tree [\-\-stdin] [\-m] [\-s] [\-v] [\-\-no\-commit\-id] [\-\-pretty] [\-t] [\-r]
+ [\-\-root] [<common diff options>] <tree\-ish> [<tree\-ish>] [<path>...]
+.fi
.SH "DESCRIPTION"
.TP
\-\-abbrev[=<n>]
-Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful dhexigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
+Instead of showing the full 40\-byte hexadecimal object name in diff\-raw format output and diff\-tree header lines, show only handful hexdigits prefix\&. This is independent of \-\-full\-index option above, which controls the diff\-patch output format\&. Non default number of digits can be specified with \-\-abbrev=<n>\&.
.TP
\-B
.TP
\-s
-By default, "git\-diff\-tree \-\-stdin" shows differences, either in machine\-readable form (without \-p) or in patch form (with \-p)\&. This output can be supressed\&. It is only useful with \-v flag\&.
+By default, "git\-diff\-tree \-\-stdin" shows differences, either in machine\-readable form (without \-p) or in patch form (with \-p)\&. This output can be suppressed\&. It is only useful with \-v flag\&.
.TP
\-v
.TP 3
1.
-It is preceeded with a "git diff" header, that looks like this:
+It is preceded with a "git diff" header, that looks like this:
.nf
instead of using the tip of the current branch, compare with the
tip of "test" branch\&.
instead of comparing with the tip of "test" branch, compare with
-the tip of the curren branch, but limit the comparison to the
+the tip of the current branch, but limit the comparison to the
file "test"\&.
compare the version before the last commit and the last commit\&.
.TP
git-format-patch \- Prepare patches for e-mail submission.
.SH "SYNOPSIS"
-
-git\-format\-patch [\-n | \-k] [\-o <dir> | \-\-stdout] [\-s] [\-c] [\-\-mbox] [\-\-diff\-options] <his> [<mine>]
+.nf
+git\-format\-patch [\-n | \-k] [\-o <dir> | \-\-stdout] [\-s] [\-c] [\-\-mbox]
+ [\-\-diff\-options] <his> [<mine>]
+.fi
.SH "DESCRIPTION"
.SH "SEE ALSO"
-\fBgit\-am\fR(1), gitlink:git\-send\-email
+\fBgit\-am\fR(1), \fBgit\-send\-email\fR(1)
.SH "AUTHOR"
git-fsck-objects \- Verifies the connectivity and validity of the objects in the database
.SH "SYNOPSIS"
-
-git\-fsck\-objects [\-\-tags] [\-\-root] [\-\-unreachable] [\-\-cache] [\-\-standalone | \-\-full] [\-\-strict] [<object>*]
+.nf
+git\-fsck\-objects [\-\-tags] [\-\-root] [\-\-unreachable] [\-\-cache]
+ [\-\-standalone | \-\-full] [\-\-strict] [<object>*]
+.fi
.SH "DESCRIPTION"
.SH "SYNOPSIS"
-git\-grep <option>... <pattern> <path>...
+git\-grep [<option>...] <pattern> [<path>...]
.SH "DESCRIPTION"
..
.TH "GIT-HTTP-FETCH" 1 "" "" ""
.SH NAME
-git-http-fetch \- Downloads a remote git repository via HTTP
+git-http-fetch \- downloads a remote git repository via HTTP
.SH "SYNOPSIS"
-git\-http\-fetch [\-c] [\-t] [\-a] [\-d] [\-v] [\-w filename] [\-\-recover] commit\-id url
+git\-http\-fetch [\-c] [\-t] [\-a] [\-d] [\-v] [\-w filename] [\-\-recover] <commit> <url>
.SH "DESCRIPTION"
.SH "SYNOPSIS"
-git\-init\-db [\-\-template=<template_directory>]
+git\-init\-db [\-\-template=<template_directory>] [\-\-shared]
.SH "OPTIONS"
\-\-template=<template_directory>
Provide the directory in from which templates will be used\&.
+.TP
+\-\-shared
+Specify that the git repository is to be shared amongst several users\&.
+
.SH "DESCRIPTION"
If the object storage directory is specified via the $GIT_OBJECT_DIRECTORY environment variable then the sha1 directories are created underneath \- otherwise the default $GIT_DIR/objects directory is used\&.
-git\-init\-db won't hurt an existing repository\&.
+A shared repository allows users belonging to the same group to push into that repository\&. When specifying \-\-shared the config variable "core\&.sharedRepository" is set to true so that directories under $GIT_DIR are made group writable (and g+sx, since the git group may be not the primary group of all users)\&.
+
+
+Running git\-init\-db in an existing repository is safe\&. It will not overwrite things that are already there\&. The primary reason for rerunning git\-init\-db is to pick up newly added templates\&.
.SH "EXAMPLES"
R
removed/deleted
C
-modifed/changed
+modified/changed
K
to be killed ? other
.TP
\-\-stdout
-Write the pack contents (what would have been writtin to \&.pack file) out to the standard output\&.
+Write the pack contents (what would have been written to \&.pack file) out to the standard output\&.
.TP
\-\-window and \-\-depth
You can query/set/replace/unset options with this command\&. The name is actually the section and the key separated by a dot, and the value will be escaped\&.
-If you want to set/unset an option which can occor on multiple lines, you should provide a POSIX regex for the value\&. If you want to handle the lines not matching the regex, just prepend a single exlamation mark in front (see EXAMPLES)\&.
+If you want to set/unset an option which can occur on multiple lines, you should provide a POSIX regex for the value\&. If you want to handle the lines not matching the regex, just prepend a single exclamation mark in front (see EXAMPLES)\&.
This command will fail if
git-rev-list \- Lists commit objects in reverse chronological order
.SH "SYNOPSIS"
-
-git\-rev\-list [ \-\-max\-count=number ] [ \-\-max\-age=timestamp ] [ \-\-min\-age=timestamp ] [ \-\-sparse ] [ \-\-no\-merges ] [ \-\-all ] [ [ \-\-merge\-order [ \-\-show\-breaks ] ] | [ \-\-topo\-order ] | ] [ \-\-parents ] [ \-\-objects [ \-\-unpacked ] ] [ \-\-pretty | \-\-header | ] [ \-\-bisect ] <commit>... [ \-\- <paths>... ]
+.nf
+git\-rev\-list [ \-\-max\-count=number ]
+ [ \-\-max\-age=timestamp ]
+ [ \-\-min\-age=timestamp ]
+ [ \-\-sparse ]
+ [ \-\-no\-merges ]
+ [ \-\-all ]
+ [ [ \-\-merge\-order [ \-\-show\-breaks ] ] | [ \-\-topo\-order ] ]
+ [ \-\-parents ]
+ [ \-\-objects [ \-\-unpacked ] ]
+ [ \-\-pretty | \-\-header ]
+ [ \-\-bisect ]
+ <commit>... [ \-\- <paths>... ]
+.fi
.SH "DESCRIPTION"
Commits marked with (|) are direct parents of commits immediately preceding the marked commit in the list\&.
-Commits marked with (^) are not parents of the immediately preceding commit\&. These "breaks" represent necessary discontinuities implied by trying to represent an arbtirary DAG in a linear form\&.
+Commits marked with (^) are not parents of the immediately preceding commit\&. These "breaks" represent necessary discontinuities implied by trying to represent an arbitrary DAG in a linear form\&.
\-\-show\-breaks is only valid if \-\-merge\-order is also specified\&.
Given N <references>, the first N lines are the one\-line description from their commit message\&. The branch head that is pointed at by $GIT_DIR/HEAD is prefixed with an asterisk * character while other heads are prefixed with a ! character\&.
-Following these N lines, one\-line log for each commit is displayed, indented N places\&. If a commit is on the I\-th branch, the I\-th indentation character shows a + sign; otherwise it shows a space\&. Each commit shows a short name that can be used as an exended SHA1 to name that commit\&.
+Following these N lines, one\-line log for each commit is displayed, indented N places\&. If a commit is on the I\-th branch, the I\-th indentation character shows a + sign; otherwise it shows a space\&. Each commit shows a short name that can be used as an extended SHA1 to name that commit\&.
The following example shows three branches, "master", "fixes" and "mhf":
.SH "SYNOPSIS"
-git\-svnimport [ \-o <branch\-for\-HEAD> ] [ \-h ] [ \-v ] [ \-d | \-D ] [ \-C <GIT_repository> ] [ \-i ] [ \-u ] [\-l limit_rev] [ \-b branch_subdir ] [ \-
t trunk_subdir ] [ \-T tag_subdir ] [ \-s start_chg ] [ \-m ] [ \-M regex ] <SVN_repository_URL> [ <path> ]
+git\-svnimport [ \-o <branch\-for\-HEAD> ] [ \-h ] [ \-v ] [ \-d | \-D ] [ \-C <GIT_repository> ] [ \-i ] [ \-u ] [\-l limit_rev] [ \-b branch_subdir ] [ \-
T trunk_subdir ] [ \-t tag_subdir ] [ \-s start_chg ] [ \-m ] [ \-M regex ] <SVN_repository_URL> [ <path> ]
.SH "DESCRIPTION"
\-s <start_rev>
Start importing at this SVN change number\&. The default is 1\&.
-When importing incementally, you might need to edit the \&.git/svn2git file\&.
+When importing incrementally, you might need to edit the \&.git/svn2git file\&.
.TP
\-i
Import\-only: don't perform a checkout after importing\&. This option ensures the working directory and index remain untouched and will not create them if they do not exist\&.
.TP
-\-t <trunk_subdir>
+\-T <trunk_subdir>
Name the SVN trunk\&. Default "trunk"\&.
.TP
-\-T <tag_subdir>
+\-t <tag_subdir>
Name the SVN subdirectory for tags\&. Default "tags"\&.
.TP
Send patch e\-mails out of "format\-patch \-\-mbox" output\&.
.TP
-\fBgit\-symbolic\-refs\fR(1)
+\fBgit\-symbolic\-ref\fR(1)
Read and modify symbolic refs\&.
.TP
projects / git.git / commitdiff