Skip to content

Commit 496db64

Browse files
committed
Merge branch 'ph/send-email'
* ph/send-email: git send-email: ask less questions when --compose is used. git send-email: add --annotate option git send-email: interpret unknown files as revision lists git send-email: make the message file name more specific.
2 parents 455d0f5 + beece9d commit 496db64

File tree

3 files changed

+207
-75
lines changed

3 files changed

+207
-75
lines changed

Documentation/git-send-email.txt

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ git-send-email - Send a collection of patches as emails
88

99
SYNOPSIS
1010
--------
11-
'git send-email' [options] <file|directory> [... file|directory]
11+
'git send-email' [options] <file|directory|rev-list options>...
1212

1313

1414
DESCRIPTION
@@ -37,9 +37,23 @@ The --bcc option must be repeated for each user you want on the bcc list.
3737
+
3838
The --cc option must be repeated for each user you want on the cc list.
3939

40+
--annotate::
41+
Review each patch you're about to send in an editor. The setting
42+
'sendemail.multiedit' defines if this will spawn one editor per patch
43+
or one for all of them at once.
44+
4045
--compose::
4146
Use $GIT_EDITOR, core.editor, $VISUAL, or $EDITOR to edit an
4247
introductory message for the patch series.
48+
+
49+
When compose is in used, git send-email gets less interactive will use the
50+
values of the headers you set there. If the body of the email (what you type
51+
after the headers and a blank line) only contains blank (or GIT: prefixed)
52+
lines, the summary won't be sent, but git-send-email will still use the
53+
Headers values if you don't removed them.
54+
+
55+
If it wasn't able to see a header in the summary it will ask you about it
56+
interactively after quitting your editor.
4357

4458
--from::
4559
Specify the sender of the emails. This will default to
@@ -183,6 +197,12 @@ Administering
183197
--[no-]validate::
184198
Perform sanity checks on patches.
185199
Currently, validation means the following:
200+
201+
--[no-]format-patch::
202+
When an argument may be understood either as a reference or as a file name,
203+
choose to understand it as a format-patch argument ('--format-patch')
204+
or as a file name ('--no-format-patch'). By default, when such a conflict
205+
occurs, git send-email will fail.
186206
+
187207
--
188208
* Warn of patches that contain lines longer than 998 characters; this
@@ -204,6 +224,12 @@ sendemail.aliasfiletype::
204224
Format of the file(s) specified in sendemail.aliasesfile. Must be
205225
one of 'mutt', 'mailrc', 'pine', or 'gnus'.
206226

227+
sendemail.multiedit::
228+
If true (default), a single editor instance will be spawned to edit
229+
files you have to edit (patches when '--annotate' is used, and the
230+
summary when '--compose' is used). If false, files will be edited one
231+
after the other, spawning a new editor each time.
232+
207233

208234
Author
209235
------

0 commit comments

Comments
 (0)