From: William Yager <will.yager@gmail•com>
To: Kevin <kevinsisco61784@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] New to this list
Date: Sun, 2 Mar 2014 21:45:10 -0600 [thread overview]
Message-ID: <7D3FD2B1-781E-4174-AD93-17C9C6AB6CCE@gmail.com> (raw)
In-Reply-To: <5313F843.2090302@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
On Mar 2, 2014, at 21:34, Kevin <kevinsisco61784@gmail•com> wrote:
> Hello. I am a developer and I wish to contribute to bitcoin. Where is
> the best place to start?
>
> --
> Kevin
Reading and learning the reference client’s source code, or doing the same for any number of non-reference-client Bitcoin projects.
Will
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2014-03-03 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 3:34 Kevin
2014-03-03 3:45 ` William Yager [this message]
2014-03-03 6:09 ` 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=7D3FD2B1-781E-4174-AD93-17C9C6AB6CCE@gmail.com \
--to=will.yager@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=kevinsisco61784@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