---
When going through git-send-email.io to teach a coworker, the biggest
missing piece was any mention of format-patch. I find that format-patch
and then send-email is a much smoother workflow when annotating or sending
multiple patches. I don't want to make the decision one way or another
for someone new to send-email, but I do think that they should be made
aware of format-patch.
I'm not subscribed to the list, please cc me in any replies.
index.html | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/index.html b/index.html
index 8ab2131..5d10787 100644
--- a/index.html
+++ b/index.html
@@ -367,6 +367,18 @@
<h3>Using --annotate every time</h3>
<pre>git config --global sendemail.annotate yes</pre>
</div>
+ <div class="well">
+ <h3>Creating and sending patches separately</h3>
+ <p>
+ Use <code>git format-patch</code> to create patch files without
+ sending them. This can be useful if you want to make changes
+ to some of the patches instead of opening your editor for
+ every single one the way <code>--annotate</code> does.
+ </p>
+ <pre>git format-patch -3</pre>
+ <p>Edit the patch files (<code>*.patch</code>), then send:</p>
+ <pre>git send-email *.patch</pre>
+ </div>
<div class="well">
<h3>"Signing off" on your commits</h3>
<p>
--
2.28.0