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
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WKNkT-0000UT-GK
for bitcoin-development@lists.sourceforge.net;
Mon, 03 Mar 2014 07:57:17 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.179 as permitted sender)
client-ip=209.85.215.179; envelope-from=laanwj@gmail.com;
helo=mail-ea0-f179.google.com;
Received: from mail-ea0-f179.google.com ([209.85.215.179])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WKNkD-0000bS-J4
for bitcoin-development@lists.sourceforge.net;
Mon, 03 Mar 2014 07:57:17 +0000
Received: by mail-ea0-f179.google.com with SMTP id q10so4282805ead.10
for <bitcoin-development@lists.sourceforge.net>;
Sun, 02 Mar 2014 23:56:55 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.204.76.7 with SMTP id a7mr6098149bkk.17.1393833415319; Sun,
02 Mar 2014 23:56:55 -0800 (PST)
Received: by 10.205.75.72 with HTTP; Sun, 2 Mar 2014 23:56:55 -0800 (PST)
In-Reply-To: <E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com>
References: <mailman.41250.1393785335.2207.bitcoin-development@lists.sourceforge.net>
<BCF42CA2-D68C-452C-9D98-E410E71B66EF@tomgeller.com>
<20140302204029.GA21339@tilt>
<CANAnSg0a+1agr+L6a0WhUz1oB__3ZMFM8SLBaRZxQnuv6D9DyA@mail.gmail.com>
<E2C84BD6-CA8D-41D3-8C1E-BCCF67087F7F@tomgeller.com>
Date: Mon, 3 Mar 2014 08:56:55 +0100
Message-ID: <CA+s+GJC20-vKrkPhBdvHMQ5U_ocuFv_AYciPTYCexhRLsggUig@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Tom Geller <tom@tomgeller.com>
Content-Type: multipart/alternative; boundary=047d7bb03bea98d0c504f3af21f8
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.0 TIME_LIMIT_EXCEEDED Exceeded time limit / deadline
X-Headers-End: 1WKNkD-0000bS-J4
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Procedure for non-tech contributions
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 07:57:17 -0000
--047d7bb03bea98d0c504f3af21f8
Content-Type: text/plain; charset=UTF-8
On Mon, Mar 3, 2014 at 12:02 AM, Tom Geller <tom@tomgeller.com> wrote:
> Anyway, this particular solution doesn't appear to be possible in this
> case, as the file isn't at
> https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes , and I
> don't believe I could copy it to the repository without going the whole git
> route. Suggestions welcome, here or privately.
>
It's not entirely trivial as you have to make sure you're editing on the
0.9 branch not the master branch, but can be done like this:
- Go to https://github.com/bitcoin/bitcoin/blob/0.9.0/doc/release-notes.md
- Click "edit"
- Make your changes and add a commit message describing the change, usually
something like 'doc: Add missing foowidget to release notes'.
Wladimir
--047d7bb03bea98d0c504f3af21f8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Mar 3, 2014 at 12:02 AM, Tom Geller <span dir=3D"ltr"><<a href=3D"ma=
ilto:tom@tomgeller.com" target=3D"_blank">tom@tomgeller.com</a>></span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"">Anyway, this particular solution doesn'=
;t appear to be possible in this case, as the file isn't at <a href=3D"=
https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes" target=3D"=
_blank">https://github.com/bitcoin/bitcoin/tree/0.9.0/doc/release-notes</a>=
, and I don't believe I could copy it to the repository without going =
the whole git route. Suggestions welcome, here or privately.<br>
</div></blockquote><div><br></div><div>It's not entirely trivial as you=
have to make sure you're editing on the 0.9 branch not the master bran=
ch, but can be done like this:</div><div><br></div><div>- Go to <a href=3D"=
https://github.com/bitcoin/bitcoin/blob/0.9.0/doc/release-notes.md">https:/=
/github.com/bitcoin/bitcoin/blob/0.9.0/doc/release-notes.md</a></div>
<div>- Click "edit"<br></div><div>- Make your changes and add a c=
ommit message describing the change, usually something like 'doc: Add m=
issing foowidget to release notes'.</div><div><br></div><div>Wladimir</=
div>
<div><br></div></div></div></div>
--047d7bb03bea98d0c504f3af21f8--
|
