From: Gavin Andresen <gavinandresen@gmail.com>
To: Frank F <frankf44@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.8.1 plan
Date: Sat, 16 Mar 2013 22:31:38 -0400 [thread overview]
Message-ID: <CABsx9T05xEPrWA4HMEd+e5aXvj_=X2hr=+Zt+2SkntKu+TvzMA@mail.gmail.com> (raw)
In-Reply-To: <CALxyHsXqoCPSc43ty-A6FLw6Z1+MVA9LjbrOOMG6tef4N8Qobg@mail.gmail.com>
> Well, he did make the bitcoin.org/may15.html page already. It would be crazy
> to change that now.
Not crazy, just inconvenient, and possibly confusing.
I'm going to be pretty stubborn about the dates. I'm just not
interested in lots of discussion about what the perfect times/dates
will be, there are much more important things that need to get done
soon.
Like hard-forking to increase the 1MB blocksize limit. This will be
good practice for that.
--
--
Gavin Andresen
next prev parent reply other threads:[~2013-03-17 2:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 1:13 [Bitcoin-development] 0.8.1 plan Gavin Andresen
2013-03-17 2:03 ` Alan Reiner
2013-03-17 2:20 ` Frank F
2013-03-17 2:31 ` Gavin Andresen [this message]
2013-03-17 15:29 ` Luke-Jr
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='CABsx9T05xEPrWA4HMEd+e5aXvj_=X2hr=+Zt+2SkntKu+TvzMA@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=frankf44@gmail.com \
/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