~sircmpwn/email-test-drive

1

[PATCH] See how srht handles attached patches

Details
Message ID
<C5Q7OP14GI2S.2RWOY5XWPXGJG@localhost>
DKIM signature
missing
Download raw message
Probably should've just asked in the sourcehut users email list...

anyway, this part would be 'merge request description',
or [PATCH 0/2] ...

I think it's a fairly common use case, as attaching files
to an email is something most users and email clients are capable of.

though it includes more context-switching, it also makes it harder
to make a mistake.

`git format-patch HEAD~2` also is simpler, more unix-y.
git-send-email.io
Details
Message ID
<160053865672.2458.1563892518340654600@static1.static1.sr.ht>
In-Reply-To
<C5Q7OP14GI2S.2RWOY5XWPXGJG@localhost> (view parent)
DKIM signature
missing
Download raw message
Hi Zach DeCook!

We got your email, but it doesn't look like a patch. Did you use git
send-email to generate it? Generally speaking, using other tools to
generate & email patches will lead to problems with your patch.

If you did use git send-email and aren't sure what the problem is,
please shoot an email to sir@cmpwn.com asking for help.
Export thread (mbox)