From: Wladimir <laanwj@gmail•com>
To: "Saïvann Carignan" <saivann@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Developer documentation on bitcoin.org
Date: Mon, 12 May 2014 08:15:04 +0200 [thread overview]
Message-ID: <CA+s+GJBpkuBroz3AAcMCvKwEgwCbuqHJUUtVoQjWiGK9kniiGw@mail.gmail.com> (raw)
In-Reply-To: <536EDBA5.2010700@gmail.com>
On Sun, May 11, 2014 at 4:08 AM, Saïvann Carignan <saivann@gmail•com> wrote:
> A new "Developer Documentation" section should be soon merged on
> bitcoin.org .
>
> Live Preview:
> http://bitcoindev.us.to/en/developer-documentation
>
> GitHub Pull Request:
> https://github.com/bitcoin/bitcoin.org/pull/393
>
> Bitcointalk Thread:
> https://bitcointalk.org/index.php?topic=511876.0
Great work!
Very nice to see thorough developer documentation on bitcoin.org.
I've already been reading it now and then and haven't found any
technical issues yet, if I do, I'll let you know.
Wladimir
next prev parent reply other threads:[~2014-05-12 6:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 2:08 Saïvann Carignan
2014-05-12 6:15 ` Wladimir [this message]
2014-05-19 22:22 ` Saïvann Carignan
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=CA+s+GJBpkuBroz3AAcMCvKwEgwCbuqHJUUtVoQjWiGK9kniiGw@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=saivann@gmail$(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