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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WslPP-0007Rq-K0
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jun 2014 04:05:39 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.180 as permitted sender)
client-ip=209.85.213.180; envelope-from=laanwj@gmail.com;
helo=mail-ig0-f180.google.com;
Received: from mail-ig0-f180.google.com ([209.85.213.180])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WslPO-0005Xy-KF
for bitcoin-development@lists.sourceforge.net;
Fri, 06 Jun 2014 04:05:39 +0000
Received: by mail-ig0-f180.google.com with SMTP id c1so230062igq.7
for <bitcoin-development@lists.sourceforge.net>;
Thu, 05 Jun 2014 21:05:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.43.136 with SMTP id w8mr1519576igl.20.1402027532513; Thu,
05 Jun 2014 21:05:32 -0700 (PDT)
Received: by 10.64.60.195 with HTTP; Thu, 5 Jun 2014 21:05:32 -0700 (PDT)
Date: Fri, 6 Jun 2014 06:05:32 +0200
Message-ID: <CA+s+GJA9ki6RUZ8S3wRW5Pev-COSotkVkL=b_6DHZnCnW4j45Q@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.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
-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
X-Headers-End: 1WslPO-0005Xy-KF
Subject: [Bitcoin-development] Do not use github issues on BIPs repository
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: Fri, 06 Jun 2014 04:05:39 -0000
Hello,
I see that people have been filing issues on the Bitcoin Improvement
Requests repository, https://github.com/bitcoin/bips.
This is not how it is supposed to work -- BIP authors are not required
to monitor the github issues, and it is not a good place to discuss in
the first place. If you have a remark about a BIP or want to discuss
it please use this mailing list (preferably) or contact the authors
some other way.
After discussion you can submit a pull request. Or if the change is
trivial, such as a typo, you can submit a pull immediately.
For this reason I intend to disable issues (not pull requests, of
course) on the repository.
Wladimir
|
