Previous: git-email-send-email, Up: Send patches [Contents][Index]
When you invoke git-email-format-patch, you will prompted in the
minibuffer for extra arguments to give git format-patch. Some common
arguments will be displayed in your completion framework. If you want
to select multiple options, separate them with , or whatever the value
of crm-separator is. You can add options to the list of candidates by
customizing git-email-format-patch-extra-args.
git-email-format-patch-default-args contains arguments automatically
passed to git format-patch if no extra arguments are given.
After you have entered extra arguments, the minibuffer will prompt you
to select the base commit for your patches. That is, a patch will be
generated for the changes between the base commit and the current
HEAD. Selecting the second candidate in the list is equivalent to
typing HEAD^1 in the shell. If you are already in a VC log buffer,
the revision under point will be used automatically.
When the revision has been selected, patches will be generated and you
will be greeted with a message buffer containing a patch, just like
with git-email-send-email. By default, the generated patches will be
deleted, if you don not like this behaviour, call
git-email-format-patch with a prefix argument (C-u).
In case you forgot to Cc someone while writing the command line options
for git format-patch, you can use
git-email-rewrite-header to add an Email address to Cc to all the
messages. If you have already put an address in the “Cc” field, and
you still want to keep that address, you can invoke
git-email-rewrite-header with a prefix argument, then the address
to specified will be appended to the “Cc” field, rather than
overwriting the old address.
Another use of git-email-rewrite-header is when you are sending a
multi-patchset series to a mailing list managed by Debbugs. You first
have to send a message to the mailing list address, then you have to
wait for an “acknowledgement” message from Debbugs that tells you the
bug number for the messages. Once you know the bug number you can send
followup messages to NNN@debbugs.gnu.org, where NNN
is the bug number. See the
Debbugs documentation for more information. Instead of having to
manually switch to every buffer and add the “To” address, you can
simply call git-email-rewrite-header, specify the “To” header,
and then the appropriate Debbugs address.
You can see all the customizable variables running M-x customize-group RET git-email RET.
Previous: git-email-send-email, Up: Send patches [Contents][Index]