blob: 86fa2f794fd8eccef7ed731a80021a3432294bc1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Copyright (C) 2020 Cem Keylan
Licensed under Gnu Free Documentation License. -->
<!-- Created by GNU Texinfo 6.7, http://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Sending Git mails (Carbs Linux User Manual)</title>
<meta name="description" content="Sending Git mails (Carbs Linux User Manual)">
<meta name="keywords" content="Sending Git mails (Carbs Linux User Manual)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<link href="index.html" rel="start" title="Top">
<link href="Contribution-Guidelines.html" rel="up" title="Contribution Guidelines">
<link href="Init-System.html" rel="next" title="Init System">
<link href="Repository-Conventions.html" rel="prev" title="Repository Conventions">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<span id="Sending-Git-mails"></span><div class="header">
<p>
Previous: <a href="Conventions.html" accesskey="p" rel="prev">Conventions</a>, Up: <a href="Contribution-Guidelines.html" accesskey="u" rel="up">Contribution Guidelines</a> </p>
</div>
<hr>
<span id="Sending-Git-mails-1"></span><h3 class="section">3.2 Sending Git mails</h3>
<p>As mentioned, the preferred way of contribution is via patches. The easiest way
for sending git mails without <code>git send-email</code> is using <code>msmtp</code>.
You can install it from the repository by doing:
</p>
<div class="example">
<pre class="example">$ cpt b msmtp && cpt i msmtp
</pre></div>
<p>You can then edit <samp>~/.config/msmtp/config</samp> to add your email. Here is an
example configuration, you can use <code>pass</code>, <code>pash</code>, or any other
password manager that fits your needs:
</p>
<div class="example">
<pre class="example">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"
</pre></div>
<p>In order to simply send your patch, do the following:
</p>
<div class="example">
<pre class="example">$ git format-patch --to=~carbslinux/dev+subscribe@lists.sr.ht -1 --stdout |
msmtp -t -a my-mail
</pre></div>
<p>You can also send multiple patches by doing the following:
</p>
<div class="example">
<pre class="example">$ 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
</pre></div>
</body>
</html>
|