From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin v0.3.24 released
Date: Sat, 9 Jul 2011 14:18:04 +0200 [thread overview]
Message-ID: <CANEZrP0aqo+Jznou5OEQvr7a1FbBoKmkZuk7A4Z+4ZG4j2vybg@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpcNx7ffKCj6HEdTmK2S+AORcZen+dfAtZyzz3fQ44+PHg@mail.gmail.com>
If there haven't been lots of upgrades in a few days, I think it's
time to use the alert function again.
next prev parent reply other threads:[~2011-07-09 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 21:35 [Bitcoin-development] Bitcoin v0.3.24 released Jeff Garzik
2011-07-09 12:18 ` Mike Hearn [this message]
2011-07-19 0:17 ` Jeff Garzik
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=CANEZrP0aqo+Jznou5OEQvr7a1FbBoKmkZuk7A4Z+4ZG4j2vybg@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.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