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
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
$ 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
static char *extra_headers = NULL;
static int extra_headers_size = 0;
-static const char *fmt_patch_suffix = ".txt";
+static const char *fmt_patch_suffix = ".patch";
static int git_format_config(const char *var, const char *value)
{