.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-CONFIG" "1" "01/29/2007" "" ""
+.TH "GIT\-CONFIG" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.nf
[section "subsection"]
.fi
-Subsection names can contain any characters except newline (doublequote \fI"\fR and backslash have to be escaped as \fI\\"\fR and \fI\\\\\fR, respecitvely) and are case sensitive. Section header cannot span multiple lines. Variables may belong directly to a section or to a given subsection. You can have [section] if you have [section "subsection"], but you don't need to.
+Subsection names can contain any characters except newline (doublequote \fI"\fR and backslash have to be escaped as \fI\\"\fR and \fI\\\\\fR, respectively) and are case sensitive. Section header cannot span multiple lines. Variables may belong directly to a section or to a given subsection. You can have [section] if you have [section "subsection"], but you don't need to.
There is also (case insensitive) alternative [section.subsection] syntax. In this syntax subsection names follow the same restrictions as for section name.
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-DIFF\-FILES" "1" "01/28/2007" "" ""
+.TH "GIT\-DIFF\-FILES" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
new file mode <mode>
deleted file mode <mode>,<mode>
.fi
-The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is diferent from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
+The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
.TP
3.
It is followed by two\-line from\-file/to\-file header
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-DIFF\-INDEX" "1" "01/28/2007" "" ""
+.TH "GIT\-DIFF\-INDEX" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
new file mode <mode>
deleted file mode <mode>,<mode>
.fi
-The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is diferent from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
+The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
.TP
3.
It is followed by two\-line from\-file/to\-file header
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-DIFF\-STAGES" "1" "01/28/2007" "" ""
+.TH "GIT\-DIFF\-STAGES" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
new file mode <mode>
deleted file mode <mode>,<mode>
.fi
-The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is diferent from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
+The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
.TP
3.
It is followed by two\-line from\-file/to\-file header
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-DIFF\-TREE" "1" "01/28/2007" "" ""
+.TH "GIT\-DIFF\-TREE" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
new file mode <mode>
deleted file mode <mode>,<mode>
.fi
-The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is diferent from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
+The mode <mode>,<mode>..<mode> line appears only if at least one of the <mode> is different from the rest. Extended headers with information about detected contents movement (renames and copying detection) are designed to work with diff of two <tree\-ish> and are not used by combined diff format.
.TP
3.
It is followed by two\-line from\-file/to\-file header
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-REMOTE" "1" "02/02/2007" "" ""
+.TH "GIT\-REMOTE" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.fi
.SH "DESCRIPTION"
Manage the set of repositories ("remotes") whose branches you track.
-
-With no arguments, shows a list of existing remotes.
-
-In the second form, adds a remote named <name> for the repository at <url>. The command git fetch <name> can then be used to create and update remote\-tracking branches <name>/<branch>.
-
-In the third form, gives some information about the remote <name>.
-
-In the fourth form, deletes all stale tracking branches under <name>. These stale branches have already been removed from the remote repository referenced by <name>, but are still locally available in "remotes/<name>".
-
+.SH "COMMANDS"
+With no arguments, shows a list of existing remotes. Several subcommands are available to perform operations on the remotes.
+.TP
+\fIadd\fR
+Adds a remote named <name> for the repository at <url>. The command git fetch <name> can then be used to create and update remote\-tracking branches <name>/<branch>.
+.TP
+\fIshow\fR
+Gives some information about the remote <name>.
+.TP
+\fIprune\fR
+Deletes all stale tracking branches under <name>. These stale branches have already been removed from the remote repository referenced by <name>, but are still locally available in "remotes/<name>".
+.SH "DISCUSSION"
The remote configuration is achieved using the remote.origin.url and remote.origin.fetch configuration variables. (See \fBgit\-config\fR(1)).
.SH "EXAMPLES"
Add a new remote, fetch, and check out a branch from it:
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SEND\-PACK" "1" "01/20/2007" "" ""
+.TH "GIT\-SEND\-PACK" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
-git\-send\-pack \- Push objects over git protocol to another reposiotory
+git\-send\-pack \- Push objects over git protocol to another repository
.SH "SYNOPSIS"
\fIgit\-send\-pack\fR [\-\-all] [\-\-force] [\-\-receive\-pack=<git\-receive\-pack>] [\-\-verbose] [\-\-thin] [<host>:]<directory> [<ref>\&...]
.SH "DESCRIPTION"
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT\-SVN" "1" "01/29/2007" "" ""
+.TH "GIT\-SVN" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
This command attempts to detect merges/branches from already imported history. Techniques used currently include regexes, file copies, and tree\-matches). This command generates (or modifies) the $GIT_DIR/info/grafts file. This command is considered experimental, and inherently flawed because merge\-tracking in SVN is inherently flawed and inconsistent across different repositories.
.TP
\fImulti\-init\fR
-This command supports git\-svnimport\-like command\-line syntax for importing repositories that are layed out as recommended by the SVN folks. This is a bit more tolerant than the git\-svnimport command\-line syntax and doesn't require the user to figure out where the repository URL ends and where the repository path begins.
+This command supports git\-svnimport\-like command\-line syntax for importing repositories that are laid out as recommended by the SVN folks. This is a bit more tolerant than the git\-svnimport command\-line syntax and doesn't require the user to figure out where the repository URL ends and where the repository path begins.
.TP
\-T<trunk_subdir> , \-\-trunk=<trunk_subdir> , \-t<tags_subdir> , \-\-tags=<tags_subdir> , \-b<branches_subdir> , \-\-branches=<branches_subdir>
These are the command\-line options for multi\-init. Each of these flags can point to a relative repository path (\-\-tags=project/tags') or a full url (\-\-tags=https://foo.org/project/tags)
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GITK" "1" "01/19/2007" "" ""
+.TH "GITK" "1" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Limit the revisions to show. This can be either a single revision meaning show from the given revision and back, or it can be a range in the form "\fI<from>\fR..\fI<to>\fR" to show all revisions between \fI<from>\fR and back to \fI<to>\fR. Note, more advanced revision selection can be applied. For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
<path>
-Limit commits to the ones touching files in the given paths. Note, to avoid ambiguity wrt. revision names use "\-\-" to separate the paths from any preceeding options.
+Limit commits to the ones touching files in the given paths. Note, to avoid ambiguity wrt. revision names use "\-\-" to separate the paths from any preceding options.
.SH "EXAMPLES"
.TP
gitk v2.6.12.. include/scsi drivers/scsi
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
-.TH "GIT" "7" "02/02/2007" "" ""
+.TH "GIT" "7" "02/04/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Duplicate another git repository on a local system.
.TP
\fBgit\-send\-pack\fR(1)
-Push objects over git protocol to another reposiotory.
+Push objects over git protocol to another repository.
.TP
\fBgit\-ssh\-fetch\fR(1)
Fetch from a remote repository over ssh connection.
My Various Git Projects / git.git / commitdiff