From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS)
Date: Sat, 24 Sep 2011 20:27:25 -0700 (PDT) [thread overview]
Message-ID: <1316921245.487.YahooMailNeo@web121002.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAHY2ayDxO035Hz0iSQvO7mj4=ryqQ+UFxy6Utv=T7nwYiuYS5w@mail.gmail.com>
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
next prev parent reply other threads:[~2011-09-25 3:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 1:04 [Bitcoin-development] Bitcoin Enhancement Proposals (BEPS) Luke-Jr
2011-09-19 3:22 ` Alex Waters
2011-09-19 16:01 ` bgroff
2011-09-19 16:57 ` Gavin Andresen
2011-09-19 17:23 ` Alex Waters
2011-09-20 2:06 ` Amir Taaki
2011-09-23 19:45 ` Daniel F
2011-09-25 3:27 ` Amir Taaki [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-19 0:31 Amir Taaki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1316921245.487.YahooMailNeo@web121002.mail.ne1.yahoo.com \
--to=zgenjix@yahoo.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox