.\" 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\-ADD" "1" "08/26/2007" "Git 1.5.3.rc6.39.g09b0" "Git Manual"
+.TH "GIT\-ADD" "1" "08/29/2007" "Git 1.5.3.rc7" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
The \fIgit status\fR command can be used to obtain a summary of which files have changes that are staged for the next commit.
-The \fIgit add\fR command will not add ignored files by default. If any ignored files were explicitly specified on the command line, \fIgit add\fR will fail with a list of ignored files. Ignored files reached by directory recursion or filename globbing will be silently ignored. The \fIadd\fR command can be used to add ignored files with the \-f (force) option.
+The \fIgit add\fR command will not add ignored files by default. If any ignored files were explicitly specified on the command line, \fIgit add\fR will fail with a list of ignored files. Ignored files reached by directory recursion or filename globbing performed by Git (quote your globs before the shell) will be silently ignored. The \fIadd\fR command can be used to add ignored files with the \-f (force) option.
Please see \fBgit\-commit\fR(1) for alternative ways to add content to a commit.
.SH "OPTIONS"
.\" 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" "08/28/2007" "Git 1.5.3.rc6.54.g9277" "Git Manual"
+.TH "GIT\-DIFF" "1" "08/29/2007" "Git 1.5.3.rc7" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
\fIgit\-diff\fR [\-\-options] <commit>..<commit> [\-\-] [<path>\&...]
This is synonymous to the previous form. If <commit> on one side is omitted, it will have the same effect as using HEAD instead.
.TP
-\fIgit\-diff\fR [\-\-options] <commit>
\&...<commit> [\-\-] [<path>\&...]
-This form is to view the changes on the branch containing and up to the second <commit>, starting at a common ancestor of both <commit>. "git\-diff A\&...B" is equivalent to "git\-diff $(git\-merge\-base A B) B". You can omit any one of <commit>, which has the same effect as using HEAD instead.
+\fIgit\-diff\fR [\-\-options] <commit>...<commit> [\-\-] [<path>\&...]
+This form is to view the changes on the branch containing and up to the second <commit>, starting at a common ancestor of both <commit>. "git\-diff A...B" is equivalent to "git\-diff $(git\-merge\-base A B) B". You can omit any one of <commit>, which has the same effect as using HEAD instead.
-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>.
+Just in case if you are doing something exotic, it should be noted that all of the <commit> in the above description, except for the last two forms that use ".." notations, 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). However, "diff" is about comparing two _endpoints_, not ranges, and the range notations ("<commit>..<commit>" and "<commit>\&...<commit>") do not mean a range as defined in the "SPECIFYING RANGES" section in \fBgit\-rev\-parse\fR(1).
+For a more complete list of ways to spell <commit>, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1). However, "diff" is about comparing two _endpoints_, not ranges, and the range notations ("<commit>..<commit>" and "<commit>...<commit>") do not mean a range as defined in the "SPECIFYING RANGES" 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" "08/25/2007" "Git 1.5.3.rc6.23.g0058" "Git Manual"
+.TH "GIT\-FORMAT\-PATCH" "1" "08/29/2007" "Git 1.5.3.rc7" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
[\-\-in\-reply\-to=Message\-Id] [\-\-suffix=.<sfx>]
[\-\-ignore\-if\-in\-upstream]
[\-\-subject\-prefix=Subject\-Prefix]
- <since>[..<until>]
+ [ <since> | <revision range> ]
.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. For a more complete list of ways to spell <since> and <until>, see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1).
+Prepare each commit with its patch in one file per commit, formatted to resemble UNIX mailbox format. The output of this command is convenient for e\-mail submission or for use with \fBgit\-am\fR(1).
-The output of this command is convenient for e\-mail submission or for use with \fBgit\-am\fR(1).
+There are two ways to specify which commits to operate on.
+.TP 3
+1.
+A single commit, <since>, specifies that the commits leading to the tip of the current branch that are not in the history that leads to the <since> to be output.
+.TP
+2.
+Generic <revision range> expression (see "SPECIFYING REVISIONS" section in \fBgit\-rev\-parse\fR(1)) means the commits in the specified range.
+
+A single commit, when interpreted as a <revision range> expression, means "everything that leads to that commit", but if you write \fIgit format\-patch <commit>\fR, the previous rule applies to that command line and you do not get "everything since the beginning of the time". If you want to format everything since project inception to one commit, say "git format\-patch \-\-root <commit>" to make it clear that it is the latter case.
By default, each output file is numbered sequentially from 1, and uses the first line of the commit message (massaged for pathname safety) as the filename. With the \-\-numbered\-files option, the output file names will only be numbers, without the first line of the commit appended. The names of the output files are printed to standard output, unless the \-\-stdout option is specified.
git\-format\-patch origin
Extract all commits which are in the current branch but not in the origin branch. For each commit a separate file is created in the current directory.
.TP
+git\-format\-patch \-\-root origin
+Extract all commits which that leads to \fIorigin\fR since the inception of the project.
+.TP
git\-format\-patch \-M \-B origin
The same as the previous one. Additionally, it detects and handles renames and complete rewrites intelligently to produce a renaming patch. A renaming patch reduces the amount of text output, and generally makes it easier to review it. Note that the "patch" program does not understand renaming patches, so use it only when you know the recipient uses git to apply your patch.
.TP
.\" 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" "08/21/2007" "Git 1.5.3.rc5.46.g23d5" "Git Manual"
+.TH "GIT\-LOG" "1" "08/29/2007" "Git 1.5.3.rc7" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
git log \-\-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
.TP
-git log \-r \-\-name\-status release..test
+git log \-\-name\-status release..test
Show the commits that are in the "test" branch but not yet in the "release" branch, along with the list of paths each commit modifies.
.TP
git log \-\-follow builtin\-rev\-list.c
.\" 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" "08/25/2007" "Git 1.5.3.rc6.23.g0058" "Git Manual"
+.TH "GIT\-SVN" "1" "08/29/2007" "Git 1.5.3.rc7" "Git Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ft
.fi
-Keep in mind that the \fI\fR\fI (asterisk) wildcard of the local ref (left of the \fR\fI\fI:\fR\fR\fI) *must\fR be the farthest right path component; however the remote wildcard may be anywhere as long as it's own independent path component (surrounded by \fI/\fR or EOL). This type of configuration is not automatically created by \fIinit\fR and should be manually entered with a text\-editor or using \fBgit\-config\fR(1)
+Keep in mind that the \fI\fR\fI (asterisk) wildcard of the local ref (right of the \fR\fI\fI:\fR\fR\fI) *must\fR be the farthest right path component; however the remote wildcard may be anywhere as long as it's own independent path component (surrounded by \fI/\fR or EOL). This type of configuration is not automatically created by \fIinit\fR and should be manually entered with a text\-editor or using \fBgit\-config\fR(1)
.SH "SEE ALSO"
\fBgit\-rebase\fR(1)
.SH "AUTHOR"
projects / git.git / commitdiff