1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "GIT-FORMAT-PATCH" 1 "" "" ""
22 git-format-patch \- Prepare patches for e-mail submission.
26 git\-format\-patch [\-n | \-k] [\-o <dir> | \-\-stdout] [\-s] [\-c] [\-\-mbox]
27 [\-\-diff\-options] <his> [<mine>]
33 Prepare each commit with its patch since <mine> head forked from <his> head, one file per patch, for e\-mail submission\&. Each output file is numbered sequentially from 1, and uses the first line of the commit message (massaged for pathname safety) as the filename\&.
36 When \-o is specified, output files are created in that directory; otherwise in the current working directory\&.
39 When \-n is specified, instead of "[PATCH] Subject", the first line is formatted as "[PATCH N/M] Subject", unless you have only one patch\&.
42 When \-\-mbox is specified, the output is formatted to resemble UNIX mailbox format, and can be concatenated together for processing with applymbox\&.
47 \-o|\-\-output\-directory <dir>
48 Use <dir> to store the resulting files, instead of the current working directory\&.
52 Name output in [PATCH n/m] format\&.
56 Do not strip/add [PATCH] from the first line of the commit log message\&.
59 \-a|\-\-author, \-d|\-\-date
60 Output From: and Date: headers for commits made by yourself as well\&. Usually these are output only for commits made by people other than yourself\&.
64 Add Signed\-off\-by: line to the commit message, using the committer identity of yourself\&.
68 Display suspicious lines in the patch\&. The definition of suspicious lines is currently the lines that has trailing whitespaces, and the lines whose indentation has a SP character immediately followed by a TAB character\&.
72 Format the output files for closer to mbox format by adding a phony Unix "From " line, so they can be concatenated together and fed to git\-applymbox\&. Implies \-\-author and \-\-date\&.
76 This flag generates the mbox formatted output to the standard output, instead of saving them into a file per patch and implies \-\-mbox\&.
81 git\-format\-patch \-k \-\-stdout R1\&.\&.R2 | git\-am \-3 \-k
82 Extract commits between revisions R1 and R2, and apply them on top of the current branch using git\-am to cherry\-pick them\&.
85 git\-format\-patch origin
86 Extract commits the current branch accumulated since it pulled from origin the last time in a patch form for e\-mail submission\&.
89 git\-format\-patch \-M \-B origin
90 The same as the previous one, except detect and handle renames and complete rewrites intelligently to produce 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 patch well, so use it only when you know the recipient uses git to apply your patch\&.
95 \fBgit\-am\fR(1), \fBgit\-send\-email\fR(1)
100 Written by Junio C Hamano <junkio@cox\&.net>
105 Documentation by Junio C Hamano and the git\-list <git@vger\&.kernel\&.org>\&.
110 Part of the \fBgit\fR(7) suite