summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <junkio@cox.net>2007-01-17 15:03:39 -0800
committerLibravatar Junio C Hamano <junkio@cox.net>2007-01-17 23:48:20 -0800
commit917a8f891f1ceeb48609f99ba3b32e022ac766f9 (patch)
treecdc42ddfc12ee467291c6bda1a05013b3e9f144e /Documentation
parentgit-format-patch: make --binary on by default (diff)
downloadtgif-917a8f891f1ceeb48609f99ba3b32e022ac766f9.tar.xz
git-format-patch: the default suffix is now .patch, not .txt
Editors often give easier handling of patch files if the filename ends with .patch, so use it instead of .txt. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/git-format-patch.txt15
-rw-r--r--Documentation/howto/rebase-from-internal-branch.txt2
2 files changed, 8 insertions, 9 deletions
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index 811c6e2e77..e7703a5000 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -81,9 +81,9 @@ OPTIONS
provide a new patch series.
--suffix=.<sfx>::
- Instead of using `.txt` as the suffix for generated
+ Instead of using `.patch` as the suffix for generated
filenames, use specifed suffix. A common alternative is
- `--suffix=.patch`.
+ `--suffix=.txt`.
+
Note that you would need to include the leading dot `.` if you
want a filename like `0001-description-of-my-change.patch`, and
@@ -93,15 +93,14 @@ not add any suffix.
CONFIGURATION
-------------
You can specify extra mail header lines to be added to each
-message in the repository configuration as follows:
+message in the repository configuration. Also you can specify
+the default suffix different from the built-in one:
+------------
[format]
headers = "Organization: git-foo\n"
-
-You can specify default suffix used:
-
-[format]
- suffix = .patch
+ suffix = .txt
+------------
EXAMPLES
diff --git a/Documentation/howto/rebase-from-internal-branch.txt b/Documentation/howto/rebase-from-internal-branch.txt
index fcd64e9b9b..3b3a5c2e69 100644
--- a/Documentation/howto/rebase-from-internal-branch.txt
+++ b/Documentation/howto/rebase-from-internal-branch.txt
@@ -106,7 +106,7 @@ prepare #2 and #3 for e-mail submission.
$ git format-patch master^^ master
-This creates two files, 0001-XXXX.txt and 0002-XXXX.txt. Send
+This creates two files, 0001-XXXX.patch and 0002-XXXX.patch. Send
them out "To: " your project maintainer and "Cc: " your mailing
list. You could use contributed script git-send-email if
your host has necessary perl modules for this, but your usual