From: John Smith <witchspace81@gmail.com>
To: Matt Corallo <bitcoin-list@bluematt.me>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Unit tests
Date: Sun, 31 Jul 2011 12:46:54 +0000 [thread overview]
Message-ID: <CAJNQ0ssw7yzQZca8s2Mw0NGQnnMD4SYh0YekSLTP6AMwAagALw@mail.gmail.com> (raw)
In-Reply-To: <1312115050.2325.1.camel@Desktop666>
[-- Attachment #1: Type: text/plain, Size: 157 bytes --]
>
> See pull 363 and 442 :)
>
Great. I really hope these get pulled ASAP, having the tests all over the
place in different forks is really confusing :(
JS
[-- Attachment #2: Type: text/html, Size: 361 bytes --]
prev parent reply other threads:[~2011-07-31 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJNQ0svOGGZ+L6ffK2RA+wq-VawkdJKeQcjo4_0socLZUpwDyg@mail.gmail.com>
2011-07-31 11:21 ` [Bitcoin-development] Unit tests John Smith
2011-07-31 12:24 ` Matt Corallo
2011-07-31 12:46 ` John Smith [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=CAJNQ0ssw7yzQZca8s2Mw0NGQnnMD4SYh0YekSLTP6AMwAagALw@mail.gmail.com \
--to=witchspace81@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=bitcoin-list@bluematt.me \
/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