~sircmpwn/email-test-drive

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

[PATCH v3] Demonstrate that I can use git send-email!

Details
Message ID
<20191027120103.387279-1-matt.snider@protonmail.com>
DKIM signature
pass
Download raw message
Patch: +1 -0
This part of the commit message goes into the email
---
 matt-snider | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 matt-snider

diff --git a/matt-snider b/matt-snider
new file mode 100644
index 0000000..66cb3d4
--- /dev/null
+++ b/matt-snider
@@ -0,0 +1 @@
+I have successfully used git send-email!
-- 
2.23.0
git-send-email.io
Details
Message ID
<157217768264.2136.4557781263352590755@static1.static1.sr.ht>
In-Reply-To
<20191027120103.387279-1-matt.snider@protonmail.com> (view parent)
DKIM signature
missing
Download raw message
Hi Matt Snider!

Thanks for the updated patch! This one looks good. Great work :)

If you want to learn more about using git send-email, be sure to check
out the additional resources on git-send-email.io. And if you don't
already have sourcehut account, consider registering:

	https://sourcehut.org

We provide mailing lists for emailing patches around, git repository
hosting, continuous integration, and more. Thanks for trying our git
send-email tutorial.

If you have any feedback on the tutorial, please write to sr.ht-discuss:

	~sircmpwn/public-inbox@lists.sr.ht

If you have any changes you'd like to make, feel free to use your new
skills to patch this tutorial! The repository is here:

	https://git.sr.ht/~sircmpwn/git-send-email.io

Send your patches to ~sircmpwn/public-inbox@lists.sr.ht. Please prefix
them with "[PATCH git-send-email.io]", by running this command after you
clone the repo:

	git config format.subjectPrefix "PATCH git-send-email.io"

Cheers!