1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
\r
6 <meta name="generator" content="AsciiDoc 7.0.1" />
\r
7 <style type="text/css">
\r
9 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
\r
11 border: 1px solid red;
\r
16 margin: 1em 5% 1em 5%;
\r
20 a:visited { color: fuchsia; }
\r
34 h1, h2, h3, h4, h5, h6 {
\r
36 font-family: sans-serif;
\r
38 margin-bottom: 0.5em;
\r
43 border-bottom: 2px solid silver;
\r
46 border-bottom: 2px solid silver;
\r
56 border: 1px solid silver;
\r
61 margin-bottom: 0.5em;
\r
71 font-family: sans-serif;
\r
78 font-family: sans-serif;
\r
82 font-family: sans-serif;
\r
84 border-top: 2px solid silver;
\r
90 padding-bottom: 0.5em;
\r
94 padding-bottom: 0.5em;
\r
98 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
\r
99 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
\r
100 div.admonitionblock {
\r
103 margin-bottom: 1.5em;
\r
105 div.admonitionblock {
\r
107 margin-bottom: 2.5em;
\r
110 div.content { /* Block element content. */
\r
114 /* Block element titles. */
\r
115 div.title, caption.title {
\r
116 font-family: sans-serif;
\r
120 margin-bottom: 0.5em;
\r
126 td div.title:first-child {
\r
129 div.content div.title:first-child {
\r
132 div.content + div.title {
\r
136 div.sidebarblock > div.content {
\r
137 background: #ffffee;
\r
138 border: 1px solid silver;
\r
142 div.listingblock > div.content {
\r
143 border: 1px solid silver;
\r
144 background: #f4f4f4;
\r
148 div.quoteblock > div.content {
\r
149 padding-left: 2.0em;
\r
151 div.quoteblock .attribution {
\r
155 div.admonitionblock .icon {
\r
156 vertical-align: top;
\r
159 text-decoration: underline;
\r
161 padding-right: 0.5em;
\r
163 div.admonitionblock td.content {
\r
164 padding-left: 0.5em;
\r
165 border-left: 2px solid silver;
\r
168 div.exampleblock > div.content {
\r
169 border-left: 2px solid silver;
\r
173 div.verseblock div.content {
\r
177 div.imageblock div.content { padding-left: 0; }
\r
178 div.imageblock img { border: 1px solid silver; }
\r
179 span.image img { border-style: none; }
\r
183 margin-bottom: 0.8em;
\r
188 font-style: italic;
\r
190 dd > *:first-child {
\r
195 list-style-position: outside;
\r
198 list-style-type: lower-alpha;
\r
201 div.tableblock > table {
\r
202 border-color: #527bbd;
\r
206 font-family: sans-serif;
\r
215 margin-bottom: 0.8em;
\r
218 vertical-align: top;
\r
219 font-style: italic;
\r
220 padding-right: 0.8em;
\r
223 vertical-align: top;
\r
227 div#footer-badges { display: none; }
\r
229 include::./stylesheets/xhtml11-manpage.css[]
\r
230 /* Workarounds for IE6's broken and incomplete CSS2. */
\r
232 div.sidebar-content {
\r
233 background: #ffffee;
\r
234 border: 1px solid silver;
\r
237 div.sidebar-title, div.image-title {
\r
238 font-family: sans-serif;
\r
241 margin-bottom: 0.5em;
\r
244 div.listingblock div.content {
\r
245 border: 1px solid silver;
\r
246 background: #f4f4f4;
\r
250 div.quoteblock-content {
\r
251 padding-left: 2.0em;
\r
254 div.exampleblock-content {
\r
255 border-left: 2px solid silver;
\r
256 padding-left: 0.5em;
\r
259 <title>git-format-patch(1)</title>
\r
264 git-format-patch(1) Manual Page
\r
267 <div class="sectionbody">
\r
268 <p>git-format-patch -
\r
269 Prepare patches for e-mail submission.
\r
274 <div class="sectionbody">
\r
275 <div class="verseblock">
\r
276 <div class="content"><em>git-format-patch</em> [-n | -k] [-o <dir> | --stdout] [-s] [-c] [--mbox]
\r
277 [--diff-options] <his> [<mine>]</div></div>
\r
279 <h2>DESCRIPTION</h2>
\r
280 <div class="sectionbody">
\r
281 <p>Prepare each commit with its patch since <mine> head forked from
\r
282 <his> head, one file per patch, for e-mail submission. Each
\r
283 output file is numbered sequentially from 1, and uses the first
\r
284 line of the commit message (massaged for pathname safety) as the
\r
286 <p>When -o is specified, output files are created in that
\r
287 directory; otherwise in the current working directory.</p>
\r
288 <p>When -n is specified, instead of "[PATCH] Subject", the first
\r
289 line is formatted as "[PATCH N/M] Subject", unless you have only
\r
291 <p>When --mbox is specified, the output is formatted to resemble
\r
292 UNIX mailbox format, and can be concatenated together for
\r
293 processing with applymbox.</p>
\r
296 <div class="sectionbody">
\r
299 -o|--output-directory <dir>
\r
303 Use <dir> to store the resulting files, instead of the
\r
304 current working directory.
\r
312 Name output in <em>[PATCH n/m]</em> format.
\r
320 Do not strip/add <em>[PATCH]</em> from the first line of the
\r
321 commit log message.
\r
325 -a|--author, -d|--date
\r
329 Output From: and Date: headers for commits made by
\r
330 yourself as well. Usually these are output only for
\r
331 commits made by people other than yourself.
\r
339 Add <tt>Signed-off-by:</tt> line to the commit message, using
\r
340 the committer identity of yourself.
\r
348 Display suspicious lines in the patch. The definition
\r
349 of <em>suspicious lines</em> is currently the lines that has
\r
350 trailing whitespaces, and the lines whose indentation
\r
351 has a SP character immediately followed by a TAB
\r
360 Format the output files for closer to mbox format by
\r
361 adding a phony Unix "From " line, so they can be
\r
362 concatenated together and fed to <tt>git-applymbox</tt>.
\r
363 Implies --author and --date.
\r
371 This flag generates the mbox formatted output to the
\r
372 standard output, instead of saving them into a file per
\r
373 patch and implies --mbox.
\r
379 <div class="sectionbody">
\r
382 git-format-patch -k --stdout R1..R2 | git-am -3 -k
\r
386 Extract commits between revisions R1 and R2, and apply
\r
387 them on top of the current branch using <tt>git-am</tt> to
\r
392 git-format-patch origin
\r
396 Extract commits the current branch accumulated since it
\r
397 pulled from origin the last time in a patch form for
\r
402 git-format-patch -M -B origin
\r
406 The same as the previous one, except detect and handle
\r
407 renames and complete rewrites intelligently to produce
\r
408 renaming patch. A renaming patch reduces the amount of
\r
409 text output, and generally makes it easier to review
\r
410 it. Note that the "patch" program does not understand
\r
411 renaming patch well, so use it only when you know the
\r
412 recipient uses git to apply your patch.
\r
418 <div class="sectionbody">
\r
419 <p><a href="git-am.html">git-am(1)</a>, <a href="git-send-email.html">git-send-email(1)</a></p>
\r
422 <div class="sectionbody">
\r
423 <p>Written by Junio C Hamano <junkio@cox.net></p>
\r
425 <h2>Documentation</h2>
\r
426 <div class="sectionbody">
\r
427 <p>Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
\r
430 <div class="sectionbody">
\r
431 <p>Part of the <a href="git.html">git(7)</a> suite</p>
\r
434 <div id="footer-text">
\r
435 Last updated 06-Jan-2006 17:12:29 PDT
\r