From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Zooko Wilcox-OHearn <zooko@leastauthority•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] (no subject)
Date: Sat, 25 May 2013 10:25:35 +0200 [thread overview]
Message-ID: <CAKaEYhKOmSc+Mz=vA-M=34aXOs=VfC0jvCP+qNSdjE_2WVUfkg@mail.gmail.com> (raw)
In-Reply-To: <CAM_a8Jwo_7NJJoaKYUYo6T7U8AsDfT5=MZSXjmdYU4330OHNmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
On 25 May 2013 07:46, Zooko Wilcox-OHearn <zooko@leastauthority•com> wrote:
> jgarzik wrote:
> > 1) Rule changes. We don't want these.
>
> In general? What constitutes a rule change?
>
> For example, if I understand correctly (from what Gavin said at
> Bitcoin 2013), there is a move afoot to lift the block size limit.
> Although, when I went to confirm my understanding by reading the
> bitcoin-development list archives, I don't see mention of this. Is
> there another forum I should be reading if I want to follow Bitcoin
> development?
>
> Anyway, I hope that there are some rule changes that you would
> consider for Bitcoin, although I recognize there are vast classes of
> such changes that you wouldn't.
>
> I'm trying to figure out what's the most productive way to show you,
> and everyone, candidates for such changes. Things that are definitely
> not suitable for merging to trunk tomorrow, but might be suitable in a
> year or two, or "Next Time We Have A Hardfork".
>
> I don't think alternative bitcoin-clones are the best venue for those.
> Although they are certainly good venues for changes which can never
> make it into Bitcoin.
>
> Perhaps the best venue for such a thing is just to fork bitcoin.git on
> github.
>
It might be an idea to have 'rule change' fixes and 'bug fix' releases go
out separately
>
> Regards,
>
> Zooko Wilcox-O'Hearn
>
> Founder, CEO, and Customer Support Rep
>
> https://LeastAuthority.com
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 3034 bytes --]
next prev parent reply other threads:[~2013-05-25 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 5:46 Zooko Wilcox-OHearn
2013-05-25 8:09 ` Wladimir
2013-05-27 2:43 ` [Bitcoin-development] Handling alerts & communication on bitcoin.org Saïvann
2013-05-25 8:25 ` Melvin Carvalho [this message]
2013-05-25 8:53 ` [Bitcoin-development] (no subject) Luke-Jr
2013-05-25 9:23 ` Melvin Carvalho
2014-05-04 1:47 losewife
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='CAKaEYhKOmSc+Mz=vA-M=34aXOs=VfC0jvCP+qNSdjE_2WVUfkg@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zooko@leastauthority$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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