summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2016-01-26 15:40:30 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-26 15:40:30 -0800
commitb2ed5ae80a1b45ac00c4c891e693ffcde34a9347 (patch)
treec71994f5b195a1c0d6e709e912fdce63b5c47b4e /Documentation
parentMerge branch 'rp/p4-filetype-change' (diff)
parentformat-patch: introduce format.outputDirectory configuration (diff)
downloadtgif-b2ed5ae80a1b45ac00c4c891e693ffcde34a9347.tar.xz
Merge branch 'ak/format-patch-odir-config'
"git format-patch" learned to notice format.outputDirectory configuration variable. This allows "-o <dir>" option to be omitted on the command line if you always use the same directory in your workflow. * ak/format-patch-odir-config: format-patch: introduce format.outputDirectory configuration
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/config.txt4
-rw-r--r--Documentation/git-format-patch.txt6
2 files changed, 9 insertions, 1 deletions
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 0f710ca3c2..877cbc875e 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -1245,6 +1245,10 @@ format.coverLetter::
format-patch is invoked, but in addition can be set to "auto", to
generate a cover-letter only when there's more than one patch.
+format.outputDirectory::
+ Set a custom directory to store the resulting files instead of the
+ current working directory.
+
filter.<driver>.clean::
The command which is used to convert the content of a worktree
file to a blob upon checkin. See linkgit:gitattributes[5] for
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index b149e09065..6821441d7d 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -57,7 +57,11 @@ The names of the output files are printed to standard
output, unless the `--stdout` option is specified.
If `-o` is specified, output files are created in <dir>. Otherwise
-they are created in the current working directory.
+they are created in the current working directory. The default path
+can be set with the 'format.outputDirectory' configuration option.
+The `-o` option takes precedence over `format.outputDirectory`.
+To store patches in the current working directory even when
+`format.outputDirectory` points elsewhere, use `-o .`.
By default, the subject of a single patch is "[PATCH] " followed by
the concatenation of lines from the commit message up to the first blank