~sircmpwn/sr.ht-dev

This thread contains a patchset. You're looking at the original emails, but you may wish to use the patch review UI. Review patch
2 2

[PATCH git-send-email.io] Add section about git format-patch

Details
Message ID
<20200925224503.10032-1-evan.gates@gmail.com>
DKIM signature
pass
Download raw message
Patch: +12 -0
---

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

[git-send-email.io/patches] build failed

builds.sr.ht
Details
Message ID
<C5WTC8ZZD7Q5.35ELUOTIV912V@cirno>
In-Reply-To
<20200925224503.10032-1-evan.gates@gmail.com> (view parent)
DKIM signature
missing
Download raw message
git-send-email.io/patches: FAILED in 21s

[Add section about git format-patch][0] from [Evan Gates][1]

[0]: https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/14092
[1]: mailto:evan.gates@gmail.com

✗ #308962 FAILED  git-send-email.io/patches/static.yml https://builds.sr.ht/~sircmpwn/job/308962
✓ #308961 SUCCESS git-send-email.io/patches/python.yml https://builds.sr.ht/~sircmpwn/job/308961
Details
Message ID
<C5WTCDJYQZGF.22D6HCBBU9T82@homura>
In-Reply-To
<20200925224503.10032-1-evan.gates@gmail.com> (view parent)
DKIM signature
fail
Download raw message
DKIM signature: fail
NACK, the purpose is to streamline the process. format-patch may be good
for you but I wouldn't introduce it to beginners given how intimidated
most people already are by this tool.
Reply to thread Export thread (mbox)