From cbd19301ee92ed4db0c5abae4bb1886ab18d4198 Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Mon, 14 Sep 2020 20:09:17 +0300 Subject: update --- src/docs/Sending-Git-mails.html | 95 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 src/docs/Sending-Git-mails.html (limited to 'src/docs/Sending-Git-mails.html') diff --git a/src/docs/Sending-Git-mails.html b/src/docs/Sending-Git-mails.html new file mode 100644 index 0000000..86fa2f7 --- /dev/null +++ b/src/docs/Sending-Git-mails.html @@ -0,0 +1,95 @@ + + + + + + +Sending Git mails (Carbs Linux User Manual) + + + + + + + + + + + + + + + + +
+

+Previous: , Up: Contribution Guidelines  

+
+
+

3.2 Sending Git mails

+ +

As mentioned, the preferred way of contribution is via patches. The easiest way +for sending git mails without git send-email is using msmtp. +You can install it from the repository by doing: +

+
+
$ cpt b msmtp && cpt i msmtp
+
+ +

You can then edit ~/.config/msmtp/config to add your email. Here is an +example configuration, you can use pass, pash, or any other +password manager that fits your needs: +

+
+
defaults
+auth on
+tls on
+tls_trust_file /etc/ssl/certs/ca-certificates.crt
+logfile ~/.config/msmtp/msmtp.log
+account my-mail
+host mail.example.com
+port 587
+from me@example.com
+user me@example.com
+passwordeval "pass my-mail"
+
+ +

In order to simply send your patch, do the following: +

+
+
$ git format-patch --to=~carbslinux/dev+subscribe@lists.sr.ht -1 --stdout |
+    msmtp -t -a my-mail
+
+ +

You can also send multiple patches by doing the following: +

+
+
$ git format-patch --to=~carbslinux/dev+subscribe@lists.sr.ht <region>
+
+Edit those files as necessary and send them.
+$ for file in *.patch; do msmtp -t -a my-mail < $patch; done
+
+ + + + + -- cgit v1.2.3