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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <zgenjix@yahoo.com>) id 1R7fNL-00061w-Ji
for bitcoin-development@lists.sourceforge.net;
Sun, 25 Sep 2011 03:27:31 +0000
X-ACL-Warn:
Received: from nm9-vm0.bullet.mail.ne1.yahoo.com ([98.138.91.67])
by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76)
id 1R7fNK-0008O2-Or for bitcoin-development@lists.sourceforge.net;
Sun, 25 Sep 2011 03:27:31 +0000
Received: from [98.138.90.48] by nm9.bullet.mail.ne1.yahoo.com with NNFMP;
25 Sep 2011 03:27:25 -0000
Received: from [98.138.89.173] by tm1.bullet.mail.ne1.yahoo.com with NNFMP;
25 Sep 2011 03:27:25 -0000
Received: from [127.0.0.1] by omp1029.mail.ne1.yahoo.com with NNFMP;
25 Sep 2011 03:27:25 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 555566.46483.bm@omp1029.mail.ne1.yahoo.com
Received: (qmail 1498 invoked by uid 60001); 25 Sep 2011 03:27:25 -0000
X-YMail-OSG: 1pESD7YVM1lI35F795.z1FQThBRrLexBsnq5Gd95Z8jiEWy
7wzGkW7QkdYwhVllUmou9KFYBeAbepIg5mVaZOVqI8qhqaQOUSntWDr31v1N
CY1TNLvFESsEJvP9AwWfX7dN2TxgHpxyW4CiK2N9.7eW311Tacshst.DYAPN
MhDU8zBn.UazXfLZdeqK2JcZNT_Cqlloz3QMqcYUHIuqyuu4RBbNErExbmJV
cQvgf17TDtM0ji3_BH.IEKmpGfehSAWAToU22TgMVuvtLm7yJrdigugISIw7
I1UoomwyGbCUBmFyTh1Zf7rGKc8Ru4dX12Ab4mhWbF29c.YeNxYmM3NIUWCX
.mjbYPu0aDOwBJ1ocQ..JSQr8saFjZkXZra91D8TkTRzKkGBytjcQQHGn1ST
jEjCEtL_JzEGDRtVKtSR4sj.7RPjAYW9yEGAIOc7YnC8vQwSlF2y9AxUxcCJ
uImmVNoTW498-
Received: from [93.97.176.250] by web121002.mail.ne1.yahoo.com via HTTP;
Sat, 24 Sep 2011 20:27:25 PDT
X-Mailer: YahooMailWebService/0.8.114.317681
References: <201109182104.45994.luke@dashjr.org>
<CAL0fb61B6bqGMhWtCgvy0xwfHQ_nvmhbb9uLJQWx3biENhVJNw@mail.gmail.com>
<21269.192.251.226.206.1316448084.squirrel@lavabit.com>
<CABsx9T0y601kjJ7ToczwhcQUoh3NZbuPa+iWwtm6-DZxZSRNPg@mail.gmail.com>
<CAHY2ayDxO035Hz0iSQvO7mj4=ryqQ+UFxy6Utv=T7nwYiuYS5w@mail.gmail.com>
Message-ID: <1316921245.487.YahooMailNeo@web121002.mail.ne1.yahoo.com>
Date: Sat, 24 Sep 2011 20:27:25 -0700 (PDT)
From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
In-Reply-To: <CAHY2ayDxO035Hz0iSQvO7mj4=ryqQ+UFxy6Utv=T7nwYiuYS5w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [98.138.91.67 listed in list.dnswl.org]
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(zgenjix[at]yahoo.com)
-0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-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: 1R7fNK-0008O2-Or
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Amir Taaki <zgenjix@yahoo.com>
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: Sun, 25 Sep 2011 03:27:31 -0000
Hey,
Names aren't too important and people were in favour of BIPs. I've moved them from BEPs to BIPs (Bitcoin Improvement Proposals).
----- Original Message -----
From: Daniel F <nanotube@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Sent: Friday, September 23, 2011 9:45 PM
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
> Does anybody besides me think maybe we should name them something
> other than "BEP" ?
>
> I'm worried we'll regret it in two years when a google for "BEP003"
> takes you to the BitTorrent EPs instead of the BitCoin EPs.
this is an excellent "painting the bikeshed" question, so i cannot
resist participation :)
imo, anyone who has any business looking at the beps (which would
generally be technically-minded people), will be smart enough to
google for "bitcoin bep003" to find what he's looking for. so i don't
see an issue, whatever acronym we end up using.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
|
