From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Anything to chat about today at 21:00 UTC ?
Date: Tue, 28 Feb 2012 13:56:26 -0500 [thread overview]
Message-ID: <CABsx9T3t_=BWJ0PvTLTS=oGxVYA1vRTD3t3Wo5D1=jfO6HG-7g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
I'll be in the #bitcoin-development IRC channel in two hours, for the
semi-regular Tuesday IRC meeting. Things that might be worth some
discussion:
+ The duplicate coinbase attack/fix, and strategy for rolling out sipa's
fix.
+ 0.6 release schedule
+ Is there anything we can do to attract a great Windows developer? (we've
got issues piling up...)
+ Multisignature next-steps: who is working on what?
Am I forgetting anything?
--
--
Gavin Andresen
[-- Attachment #2: Type: text/html, Size: 709 bytes --]
next reply other threads:[~2012-02-28 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:56 Gavin Andresen [this message]
2012-02-28 19:33 ` D.H.
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='CABsx9T3t_=BWJ0PvTLTS=oGxVYA1vRTD3t3Wo5D1=jfO6HG-7g@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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