<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 7.0.1" />\r
+<meta name="generator" content="AsciiDoc 7.0.2" />\r
<style type="text/css">\r
/* Debug borders */\r
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {\r
<h2>NAME</h2>\r
<div class="sectionbody">\r
<p>git-format-patch -\r
- Prepare patches for e-mail submission.\r
+ Prepare patches for e-mail submission\r
</p>\r
</div>\r
</div>\r
<h2>SYNOPSIS</h2>\r
<div class="sectionbody">\r
<div class="verseblock">\r
-<div class="content"><em>git-format-patch</em> [-n | -k] [-o <dir> | --stdout] [-s] [-c] [--mbox]\r
- [--diff-options] <his> [<mine>]</div></div>\r
+<div class="content"><em>git-format-patch</em> [-n | -k] [-o <dir> | --stdout] [--attach]\r
+ [-s | --signoff] [--diff-options] [--start-number <n>]\r
+ <since>[..<until>]</div></div>\r
</div>\r
<h2>DESCRIPTION</h2>\r
<div class="sectionbody">\r
-<p>Prepare each commit with its patch since <mine> head forked from\r
-<his> head, one file per patch, for e-mail submission. Each\r
-output file is numbered sequentially from 1, and uses the first\r
-line of the commit message (massaged for pathname safety) as the\r
-filename.</p>\r
-<p>When -o is specified, output files are created in that\r
-directory; otherwise in the current working directory.</p>\r
-<p>When -n is specified, instead of "[PATCH] Subject", the first\r
-line is formatted as "[PATCH N/M] Subject", unless you have only\r
-one patch.</p>\r
-<p>When --mbox is specified, the output is formatted to resemble\r
-UNIX mailbox format, and can be concatenated together for\r
-processing with applymbox.</p>\r
+<p>Prepare each commit between <since> and <until> with its patch in\r
+one file per commit, formatted to resemble UNIX mailbox format.\r
+If ..<until> is not specified, the head of the current working\r
+tree is implied.</p>\r
+<p>The output of this command is convenient for e-mail submission or\r
+for use with <a href="git-am.html">git-am(1)</a>.</p>\r
+<p>Each output file is numbered sequentially from 1, and uses the\r
+first line of the commit message (massaged for pathname safety) as\r
+the filename. The names of the output files are printed to standard\r
+output, unless the --stdout option is specified.</p>\r
+<p>If -o is specified, output files are created in <dir>. Otherwise\r
+they are created in the current working directory.</p>\r
+<p>If -n is specified, instead of "[PATCH] Subject", the first line\r
+is formatted as "[PATCH n/m] Subject".</p>\r
</div>\r
<h2>OPTIONS</h2>\r
<div class="sectionbody">\r
</p>\r
</dd>\r
<dt>\r
--k|--keep-subject\r
+--start-number <n>\r
</dt>\r
<dd>\r
<p>\r
- Do not strip/add <em>[PATCH]</em> from the first line of the\r
- commit log message.\r
+ Start numbering the patches at <n> instead of 1.\r
</p>\r
</dd>\r
<dt>\r
--a|--author, -d|--date\r
+-k|--keep-subject\r
</dt>\r
<dd>\r
<p>\r
- Output From: and Date: headers for commits made by\r
- yourself as well. Usually these are output only for\r
- commits made by people other than yourself.\r
+ Do not strip/add <em>[PATCH]</em> from the first line of the\r
+ commit log message.\r
</p>\r
</dd>\r
<dt>\r
</p>\r
</dd>\r
<dt>\r
--c|--check\r
-</dt>\r
-<dd>\r
-<p>\r
- Display suspicious lines in the patch. The definition\r
- of <em>suspicious lines</em> is currently the lines that has\r
- trailing whitespaces, and the lines whose indentation\r
- has a SP character immediately followed by a TAB\r
- character.\r
-</p>\r
-</dd>\r
-<dt>\r
--m|--mbox\r
+--stdout\r
</dt>\r
<dd>\r
<p>\r
- Format the output files for closer to mbox format by\r
- adding a phony Unix "From " line, so they can be\r
- concatenated together and fed to <tt>git-applymbox</tt>.\r
- Implies --author and --date.\r
+ Print all commits to the standard output in mbox format,\r
+ instead of creating a file for each one.\r
</p>\r
</dd>\r
<dt>\r
---stdout\r
+--attach\r
</dt>\r
<dd>\r
<p>\r
- This flag generates the mbox formatted output to the\r
- standard output, instead of saving them into a file per\r
- patch and implies --mbox.\r
+ Create attachments instead of inlining patches.\r
</p>\r
</dd>\r
</dl>\r
</div>\r
+<h2>CONFIGURATION</h2>\r
+<div class="sectionbody">\r
+<p>You can specify extra mail header lines to be added to each\r
+message in the repository configuration as follows:</p>\r
+<div class="literalblock">\r
+<div class="content">\r
+<pre><tt>headers = "Organization: git-foo\n"</tt></pre>\r
+</div></div>\r
+</div>\r
<h2>EXAMPLES</h2>\r
<div class="sectionbody">\r
<dl>\r
</dt>\r
<dd>\r
<p>\r
- Extract commits the current branch accumulated since it\r
- pulled from origin the last time in a patch form for\r
- e-mail submission.\r
+ Extract all commits which are in the current branch but\r
+ not in the origin branch. For each commit a separate file\r
+ is created in the current directory.\r
</p>\r
</dd>\r
<dt>\r
</dt>\r
<dd>\r
<p>\r
- The same as the previous one, except detect and handle\r
- renames and complete rewrites intelligently to produce\r
- renaming patch. A renaming patch reduces the amount of\r
- text output, and generally makes it easier to review\r
- it. Note that the "patch" program does not understand\r
- renaming patch well, so use it only when you know the\r
- recipient uses git to apply your patch.\r
+ The same as the previous one. Additionally, it detects\r
+ and handles renames and complete rewrites intelligently to\r
+ produce a renaming patch. A renaming patch reduces the\r
+ amount of text output, and generally makes it easier to\r
+ review it. Note that the "patch" program does not\r
+ understand renaming patches, so use it only when you know\r
+ the recipient uses git to apply your patch.\r
</p>\r
</dd>\r
</dl>\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 06-Jan-2006 17:12:29 PDT\r
+Last updated 06-Jun-2006 21:58:27 UTC\r
</div>\r
</div>\r
</body>\r
projects / git.git / blobdiff