.\" 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\-CHERRY\-PICK" "1" "10/06/2006" "" ""
+.TH "GIT\-CHERRY\-PICK" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
git\-cherry\-pick \- Apply the change introduced by an existing commit
.SH "SYNOPSIS"
\fIgit\-cherry\-pick\fR [\-\-edit] [\-n] [\-x] <commit>
-.sp
.SH "DESCRIPTION"
Given one existing commit, apply the change the patch introduces, and record a new commit that records it. This requires your working tree to be clean (no modifications from the HEAD commit).
-.sp
.SH "OPTIONS"
.TP
<commit>
-Commit to cherry\-pick.
+Commit to cherry\-pick. For a more complete list of ways to spell commits, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
\-e|\-\-edit
-With this option,
-git\-cherry\-pick
-will let you edit the commit message prior committing.
+With this option, git\-cherry\-pick will let you edit the commit message prior committing.
.TP
\-x
Cause the command to append which commit was cherry\-picked after the original commit message when making a commit. Do not use this option if you are cherry\-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry\-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.
.TP
\-r|\-\-replay
-It used to be that the command defaulted to do
-\-x
-described above, and
-\-r
-was to disable it. Now the default is not to do
-\-x
-so this option is a no\-op.
+It used to be that the command defaulted to do \-x described above, and \-r was to disable it. Now the default is not to do \-x so this option is a no\-op.
.TP
\-n|\-\-no\-commit
Usually the command automatically creates a commit with a commit log message stating which commit was cherry\-picked. This flag applies the change necessary to cherry\-pick the named commit to your working tree, but does not make the commit. In addition, when this option is used, your working tree does not have to match the HEAD commit. The cherry\-pick is done against the beginning state of your working tree.
-.sp
+
This is useful when cherry\-picking more than one commits' effect to your working tree in a row.
.SH "AUTHOR"
Written by Junio C Hamano <junkio@cox.net>
-.sp
.SH "DOCUMENTATION"
Documentation by Junio C Hamano and the git\-list <git@vger.kernel.org>.
-.sp
.SH "GIT"
Part of the \fBgit\fR(7) suite
-.sp
+
.\" 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" "1" "12/26/2006" "" ""
+.TH "GIT\-DIFF" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
This form is to view the changes between two <commit>, for example, tips of two branches.
Just in case if you are doing something exotic, it should be noted that all of the <commit> in the above description can be any <tree\-ish>.
+
+For a more complete list of ways to spell <commit>, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.SH "OPTIONS"
.TP
\-p
.\" 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\-FORMAT\-PATCH" "1" "01/17/2007" "" ""
+.TH "GIT\-FORMAT\-PATCH" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
<since>[..<until>]
.fi
.SH "DESCRIPTION"
-Prepare each commit between <since> and <until> with its patch in one file per commit, formatted to resemble UNIX mailbox format. If ..<until> is not specified, the head of the current working tree is implied.
+Prepare each commit between <since> and <until> with its patch in one file per commit, formatted to resemble UNIX mailbox format. If ..<until> is not specified, the head of the current working tree is implied. For a more complete list of ways to spell <since> and <until>, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
The output of this command is convenient for e\-mail submission or for use with \fBgit\-am\fR(1).
.\" 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\-LOG" "1" "01/15/2007" "" ""
+.TH "GIT\-LOG" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
Limits the number of commits to show.
.TP
<since>..<until>
-Show only commits between the named two commits. When either <since> or <until> is omitted, it defaults to HEAD, i.e. the tip of the current branch.
+Show only commits between the named two commits. When either <since> or <until> is omitted, it defaults to HEAD, i.e. the tip of the current branch. For a more complete list of ways to spell <since> and <until>, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
\-p
Show the change the commit introduces in a patch form.
.\" 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\-REV\-PARSE" "1" "11/08/2006" "" ""
+.TH "GIT\-REV\-PARSE" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
git\-rev\-parse \- Pick out and massage parameters
.SH "SYNOPSIS"
\fIgit\-rev\-parse\fR [ \-\-option ] <args>\&...
-.sp
.SH "DESCRIPTION"
Many git porcelainish commands take mixture of flags (i.e. parameters that begin with a dash \fI\-\fR) and parameters meant for underlying git\-rev\-list command they use internally and flags and parameters for other commands they use as the downstream of git\-rev\-list. This command is used to distinguish between them.
-.sp
.SH "OPTIONS"
.TP
\-\-revs\-only
-Do not output flags and parameters not meant for
-git\-rev\-list
-command.
+Do not output flags and parameters not meant for git\-rev\-list command.
.TP
\-\-no\-revs
-Do not output flags and parameters meant for
-git\-rev\-list
-command.
+Do not output flags and parameters meant for git\-rev\-list command.
.TP
\-\-flags
Do not output non\-flag parameters.
Do not output flag parameters.
.TP
\-\-default <arg>
-If there is no parameter given by the user, use
-<arg>
-instead.
+If there is no parameter given by the user, use <arg> instead.
.TP
\-\-verify
The parameter given must be usable as a single, valid object name. Otherwise barf and abort.
.TP
\-\-sq
-Usually the output is made one line per flag and parameter. This option makes output a single line, properly quoted for consumption by shell. Useful when you expect your parameter to contain whitespaces and newlines (e.g. when using pickaxe
-\-S
-with
-git\-diff\-*).
+Usually the output is made one line per flag and parameter. This option makes output a single line, properly quoted for consumption by shell. Useful when you expect your parameter to contain whitespaces and newlines (e.g. when using pickaxe \-S with git\-diff\-*).
.TP
\-\-not
-When showing object names, prefix them with
-\fI^\fR
-and strip
-\fI^\fR
-prefix from the object names that already have one.
+When showing object names, prefix them with \fI^\fR and strip \fI^\fR prefix from the object names that already have one.
.TP
\-\-symbolic
-Usually the object names are output in SHA1 form (with possible
-\fI^\fR
-prefix); this option makes them output in a form as close to the original input as possible.
+Usually the object names are output in SHA1 form (with possible \fI^\fR prefix); this option makes them output in a form as close to the original input as possible.
.TP
\-\-all
-Show all refs found in
-$GIT_DIR/refs.
+Show all refs found in $GIT_DIR/refs.
.TP
\-\-branches
-Show branch refs found in
-$GIT_DIR/refs/heads.
+Show branch refs found in $GIT_DIR/refs/heads.
.TP
\-\-tags
-Show tag refs found in
-$GIT_DIR/refs/tags.
+Show tag refs found in $GIT_DIR/refs/tags.
.TP
\-\-remotes
-Show tag refs found in
-$GIT_DIR/refs/remotes.
+Show tag refs found in $GIT_DIR/refs/remotes.
.TP
\-\-show\-prefix
When the command is invoked from a subdirectory, show the path of the current directory relative to the top\-level directory.
When the command is invoked from a subdirectory, show the path of the top\-level directory relative to the current directory (typically a sequence of "../", or an empty string).
.TP
\-\-git\-dir
-Show
-$GIT_DIR
-if defined else show the path to the .git directory.
+Show $GIT_DIR if defined else show the path to the .git directory.
.TP
\-\-short, \-\-short=number
Instead of outputting the full SHA1 values of object names try to abbreviate them to a shorter unique name. When no length is specified 7 is used. The minimum length is 4.
Flags and parameters to be parsed.
.SH "SPECIFYING REVISIONS"
A revision parameter typically, but not necessarily, names a commit object. They use what is called an \fIextended SHA1\fR syntax. Here are various ways to spell object names. The ones listed near the end of this list are to name trees and blobs contained in a commit.
-.sp
.TP 3
\(bu
The full SHA1 object name (40\-byte hexadecimal string), or a substring of such that is unique within the repository. E.g. dae86e1950b1277e545cee180551750029cfe735 and dae86e both name the same commit object if there are no other object in your repository whose object name starts with dae86e.
.TP
\(bu
-An output from
-git\-describe; i.e. a closest tag, followed by a dash, a
-g, and an abbreviated object name.
+An output from git\-describe; i.e. a closest tag, followed by a dash, a g, and an abbreviated object name.
.TP
\(bu
-A symbolic ref name. E.g.
-\fImaster\fR
-typically means the commit object referenced by $GIT_DIR/refs/heads/master. If you happen to have both heads/master and tags/master, you can explicitly say
-\fIheads/master\fR
-to tell git which one you mean. When ambiguous, a
-<name>
-is disambiguated by taking the first match in the following rules:
+A symbolic ref name. E.g. \fImaster\fR typically means the commit object referenced by $GIT_DIR/refs/heads/master. If you happen to have both heads/master and tags/master, you can explicitly say \fIheads/master\fR to tell git which one you mean. When ambiguous, a <name> is disambiguated by taking the first match in the following rules:
.RS
.TP 3
1.
-if
-$GIT_DIR/<name>
-exists, that is what you mean (this is usually useful only for
-HEAD,
-FETCH_HEAD
-and
-MERGE_HEAD);
+if $GIT_DIR/<name> exists, that is what you mean (this is usually useful only for HEAD, FETCH_HEAD and MERGE_HEAD);
.TP
2.
-otherwise,
-$GIT_DIR/refs/<name>
-if exists;
+otherwise, $GIT_DIR/refs/<name> if exists;
.TP
3.
-otherwise,
-$GIT_DIR/refs/tags/<name>
-if exists;
+otherwise, $GIT_DIR/refs/tags/<name> if exists;
.TP
4.
-otherwise,
-$GIT_DIR/refs/heads/<name>
-if exists;
+otherwise, $GIT_DIR/refs/heads/<name> if exists;
.TP
5.
-otherwise,
-$GIT_DIR/refs/remotes/<name>
-if exists;
+otherwise, $GIT_DIR/refs/remotes/<name> if exists;
.TP
6.
-otherwise,
-$GIT_DIR/refs/remotes/<name>/HEAD
-if exists.
+otherwise, $GIT_DIR/refs/remotes/<name>/HEAD if exists.
.RE
.TP
\(bu
-A ref followed by the suffix
-\fI@\fR
-with a date specification enclosed in a brace pair (e.g.
-\fI{yesterday}\fR,
-\fI{1 month 2 weeks 3 days 1 hour 1 second ago}\fR
-or
-\fI{1979\-02\-26 18:30:00}\fR) to specify the value of the ref at a prior point in time. This suffix may only be used immediately following a ref name and the ref must have an existing log ($GIT_DIR/logs/<ref>).
+A ref followed by the suffix \fI@\fR with a date specification enclosed in a brace pair (e.g. \fI{yesterday}\fR, \fI{1 month 2 weeks 3 days 1 hour 1 second ago}\fR or \fI{1979\-02\-26 18:30:00}\fR) to specify the value of the ref at a prior point in time. This suffix may only be used immediately following a ref name and the ref must have an existing log ($GIT_DIR/logs/<ref>).
+.TP
+\(bu
+A ref followed by the suffix \fI@\fR with an ordinal specification enclosed in a brace pair (e.g. \fI{1}\fR, \fI{15}\fR) to specify the n\-th prior value of that ref. For example \fImaster@{1}\fR is the immediate prior value of \fImaster\fR while \fImaster@{5}\fR is the 5th prior value of \fImaster\fR. This suffix may only be used immediately following a ref name and the ref must have an existing log ($GIT_DIR/logs/<ref>).
.TP
\(bu
-A suffix
-\fI^\fR
-to a revision parameter means the first parent of that commit object.
-\fI^<n>\fR
-means the <n>th parent (i.e.
-\fIrev^\fR
-is equivalent to
-\fIrev^1\fR). As a special rule,
-\fIrev^0\fR
-means the commit itself and is used when
-\fIrev\fR
-is the object name of a tag object that refers to a commit object.
+A suffix \fI^\fR to a revision parameter means the first parent of that commit object. \fI^<n>\fR means the <n>th parent (i.e. \fIrev^\fR is equivalent to \fIrev^1\fR). As a special rule, \fIrev^0\fR means the commit itself and is used when \fIrev\fR is the object name of a tag object that refers to a commit object.
.TP
\(bu
-A suffix
-\fI~<n>\fR
-to a revision parameter means the commit object that is the <n>th generation grand\-parent of the named commit object, following only the first parent. I.e. rev~3 is equivalent to rev^^^ which is equivalent to rev^1^1^1. See below for a illustration of the usage of this form.
+A suffix \fI~<n>\fR to a revision parameter means the commit object that is the <n>th generation grand\-parent of the named commit object, following only the first parent. I.e. rev~3 is equivalent to rev^^^ which is equivalent to rev^1^1^1. See below for a illustration of the usage of this form.
.TP
\(bu
-A suffix
-\fI^\fR
-followed by an object type name enclosed in brace pair (e.g.
-v0.99.8^{commit}) means the object could be a tag, and dereference the tag recursively until an object of that type is found or the object cannot be dereferenced anymore (in which case, barf).
-rev^0
-introduced earlier is a short\-hand for
-rev^{commit}.
+A suffix \fI^\fR followed by an object type name enclosed in brace pair (e.g. v0.99.8^{commit}) means the object could be a tag, and dereference the tag recursively until an object of that type is found or the object cannot be dereferenced anymore (in which case, barf). rev^0 introduced earlier is a short\-hand for rev^{commit}.
.TP
\(bu
-A suffix
-\fI^\fR
-followed by an empty brace pair (e.g.
-v0.99.8^{}) means the object could be a tag, and dereference the tag recursively until a non\-tag object is found.
+A suffix \fI^\fR followed by an empty brace pair (e.g. v0.99.8^{}) means the object could be a tag, and dereference the tag recursively until a non\-tag object is found.
.TP
\(bu
-A suffix
-\fI:\fR
-followed by a path; this names the blob or tree at the given path in the tree\-ish object named by the part before the colon.
+A suffix \fI:\fR followed by a path; this names the blob or tree at the given path in the tree\-ish object named by the part before the colon.
.TP
\(bu
A colon, optionally followed by a stage number (0 to 3) and a colon, followed by a path; this names a blob object in the index at the given path. Missing stage number (and the colon that follows it) names an stage 0 entry.
+
Here is an illustration, by Jon Loeliger. Both node B and C are a commit parents of commit node A. Parent commits are ordered left\-to\-right.
.sp
-.sp
.nf
G H I J
\\ / \\ /
.fi
.SH "SPECIFYING RANGES"
History traversing commands such as git\-log operate on a set of commits, not just a single commit. To these commands, specifying a single revision with the notation described in the previous section means the set of commits reachable from that commit, following the commit ancestry chain.
-.sp
+
To exclude commits reachable from a commit, a prefix ^ notation is used. E.g. "^r1 r2" means commits reachable from r2 but exclude the ones reachable from r1.
-.sp
+
This set operation appears so often that there is a shorthand for it. "r1..r2" is equivalent to "^r1 r2". It is the difference of two sets (subtract the set of commits reachable from r1 from the set of commits reachable from r2).
-.sp
+
A similar notation "r1...r2" is called symmetric difference of r1 and r2 and is defined as "r1 r2 \-\-not $(git\-merge\-base \-\-all r1 r2)". It it the set of commits that are reachable from either one of r1 or r2 but not from both.
-.sp
+
Two other shorthands for naming a set that is formed by a commit and its parent commits exists. r1^@ notation means all parents of r1. r1^! includes commit r1 but excludes its all parents.
-.sp
+
Here are a handful examples:
.sp
-.sp
.nf
D A B D
D F A B C D F
.fi
.SH "AUTHOR"
Written by Linus Torvalds <torvalds@osdl.org> and Junio C Hamano <junkio@cox.net>
-.sp
.SH "DOCUMENTATION"
Documentation by Junio C Hamano and the git\-list <git@vger.kernel.org>.
-.sp
.SH "GIT"
Part of the \fBgit\fR(7) suite
-.sp
+
.\" 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\-REVERT" "1" "10/03/2006" "" ""
+.TH "GIT\-REVERT" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
git\-revert \- Revert an existing commit
.SH "SYNOPSIS"
\fIgit\-revert\fR [\-\-edit | \-\-no\-edit] [\-n] <commit>
-.sp
.SH "DESCRIPTION"
Given one existing commit, revert the change the patch introduces, and record a new commit that records it. This requires your working tree to be clean (no modifications from the HEAD commit).
-.sp
.SH "OPTIONS"
.TP
<commit>
-Commit to revert.
+Commit to revert. For a more complete list of ways to spell commit names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
\-e|\-\-edit
-With this option,
-git\-revert
-will let you edit the commit message prior committing the revert. This is the default if you run the command from a terminal.
+With this option, git\-revert will let you edit the commit message prior committing the revert. This is the default if you run the command from a terminal.
.TP
\-\-no\-edit
-With this option,
-git\-revert
-will not start the commit message editor.
+With this option, git\-revert will not start the commit message editor.
.TP
\-n|\-\-no\-commit
Usually the command automatically creates a commit with a commit log message stating which commit was reverted. This flag applies the change necessary to revert the named commit to your working tree, but does not make the commit. In addition, when this option is used, your working tree does not have to match the HEAD commit. The revert is done against the beginning state of your working tree.
-.sp
+
This is useful when reverting more than one commits' effect to your working tree in a row.
.SH "AUTHOR"
Written by Junio C Hamano <junkio@cox.net>
-.sp
.SH "DOCUMENTATION"
Documentation by Junio C Hamano and the git\-list <git@vger.kernel.org>.
-.sp
.SH "GIT"
Part of the \fBgit\fR(7) suite
-.sp
+
.\" 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\-SHOW" "1" "12/31/2006" "" ""
+.TH "GIT\-SHOW" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.SH "OPTIONS"
.TP
<object>
-The name of the object to show.
+The name of the object to show. For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
.TP
\-\-pretty[=\fI<format>\fR]
Pretty\-prints the details of a commit. \-\-pretty without an explicit =<format> defaults to \fImedium\fR. If the commit is a merge, and if the pretty\-format is not \fIoneline\fR, \fIemail\fR or \fIraw\fR, an additional line is inserted before the \fIAuthor:\fR line. This line begins with "Merge: " and the sha1s of ancestral commits are printed, separated by spaces. Note that the listed commits may not necessarily be the list of the \fBdirect\fR parent commits if you have limited your view of history: for example, if you are only interested in changes related to a certain directory or file. Here are some additional details for each format:
.\" 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" "10/03/2006" "" ""
+.TH "GITK" "1" "01/18/2007" "" ""
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
gitk \- git repository browser
.SH "SYNOPSIS"
\fIgitk\fR [<option>\&...] [<revs>] [\-\-] [<path>\&...]
-.sp
.SH "DESCRIPTION"
Displays changes in a repository or a selected set of commits. This includes visualizing the commit graph, showing information related to each commit, and the files in the trees of each revision.
-.sp
+
Historically, gitk was the first repository browser. It's written in tcl/tk and started off in a separate repository but was later merged into the main git repository.
-.sp
.SH "OPTIONS"
To control which revisions to shown, the command takes options applicable to the \fBgit\-rev\-list\fR(1) command. This manual page describes only the most frequently used options.
-.sp
.TP
\-n <number>, \-\-max\-count=<number>
Limits the number of commits to show.
Show all branches.
.TP
<revs>
-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.
+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.
.SH "EXAMPLES"
.TP
gitk v2.6.12.. include/scsi drivers/scsi
-Show as the changes since version
-\fIv2.6.12\fR
-that changed any file in the include/scsi or drivers/scsi subdirectories
+Show as the changes since version \fIv2.6.12\fR that changed any file in the include/scsi or drivers/scsi subdirectories
.TP
gitk \-\-since="2 weeks ago" \-\- gitk
-Show the changes during the last two weeks to the file
-\fIgitk\fR. The "\-\-" is necessary to avoid confusion with the
-\fBbranch\fR
-named
-\fIgitk\fR
+Show the changes during the last two weeks to the file \fIgitk\fR. The "\-\-" is necessary to avoid confusion with the \fBbranch\fR named \fIgitk\fR
.TP
gitk \-\-max\-count=100 \-\-all \(em Makefile
-Show at most 100 changes made to the file
-\fIMakefile\fR. Instead of only looking for changes in the current branch look in all branches.
+Show at most 100 changes made to the file \fIMakefile\fR. Instead of only looking for changes in the current branch look in all branches.
.SH "SEE ALSO"
.TP
\fIqgit(1)\fR
A repository browser written in C++ using Qt.
.TP
\fIgitview(1)\fR
-A repository browser written in Python using Gtk. It's based on
-\fIbzrk(1)\fR
-and distributed in the contrib area of the git repository.
+A repository browser written in Python using Gtk. It's based on \fIbzrk(1)\fR and distributed in the contrib area of the git repository.
.TP
\fItig(1)\fR
A minimal repository browser and git tool output highlighter written in C using Ncurses.
.SH "AUTHOR"
Written by Paul Mackerras <paulus@samba.org>.
-.sp
.SH "DOCUMENTATION"
Documentation by Junio C Hamano, Jonas Fonseca, and the git\-list <git@vger.kernel.org>.
-.sp
.SH "GIT"
Part of the \fBgit\fR(7) suite
-.sp
+
projects / git.git / commitdiff