From: Gavin Andresen <gavinandresen@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin 0.4.0 released
Date: Fri, 23 Sep 2011 17:36:56 -0400 [thread overview]
Message-ID: <CABsx9T0HnBzBgo57MSPNcSkjPLZeV_73JA8DhS0rA1RZJ1FchQ@mail.gmail.com> (raw)
In-Reply-To: <CAHY2ayAwG2GiDR7Cn-CTryXzFLXd=T2Nx=VCVbj9awrB6TDxDg@mail.gmail.com>
> as long as it's gpg-signed, what's the difference where it is posted?
What Daniel said. Although I did upload the signatures to github, too:
https://github.com/bitcoin/bitcoin/downloads
The github downloads have been unreliable, so I didn't announce that
you can download from there.
--
--
Gavin Andresen
prev parent reply other threads:[~2011-09-23 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 18:09 Gavin Andresen
2011-09-23 19:42 ` Andreas Schildbach
2011-09-23 21:18 ` Daniel F
2011-09-23 21:36 ` Gavin Andresen [this message]
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=CABsx9T0HnBzBgo57MSPNcSkjPLZeV_73JA8DhS0rA1RZJ1FchQ@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