From: Alex Waters <ampedal@gmail•com>
To: Matt Corallo <bitcoin-list@bluematt•me>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Testing commits
Date: Fri, 9 Sep 2011 06:08:27 -0400 [thread overview]
Message-ID: <CAL0fb61T9gnXytVx4F7yOk_3iS3QDkyVYJ-eCY-QKfrmi7b5LQ@mail.gmail.com> (raw)
In-Reply-To: <1315367465.2697.4.camel@BMThinkPad.lan.bluematt.me>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
I expect that I will make a lot of mistakes, and probably ask too many
questions - but I hope you can bear with me.
I've been trying to keep a low profile as I get better acquainted with the
project. I'm clearly in the company of some very smart people - and would
like to keep it that way.
I've tried to do my research on the main contributors, and it seems that
Matt is the only one to escape my Google stalking. If you have any questions
about my background - feel free to inquire.
It's difficult to ascertain what needs QA work first, so any guidance or
suggestion is appreciated. I'm available via social networks, email, phone,
fax?, IM, IRC, etc. Let me know your preference, or don't and I'll bugger
off.
I'll try to stay out of the way, and do my best to make the development
cycle easier. Let me know if I'm stepping on toes, or being annoying. I
won't be offended.
As for the commit testing, I want to have an idiot proof solution to get as
many people testing as possible (eventually). With code like this, I think
it's better to go full-auto with the ACKs.
-Alex
[-- Attachment #2: Type: text/html, Size: 1281 bytes --]
prev parent reply other threads:[~2011-09-09 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 0:32 Alex Waters
2011-09-07 2:59 ` Jeff Garzik
2011-09-07 3:51 ` Matt Corallo
2011-09-09 10:08 ` Alex Waters [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=CAL0fb61T9gnXytVx4F7yOk_3iS3QDkyVYJ-eCY-QKfrmi7b5LQ@mail.gmail.com \
--to=ampedal@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/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