public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Hendricks <michael@ndrix.org>
To: Jeff Garzik <jgarzik@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [PATCH] bitcoind: whitelist nodes, to prevent them from being banned
Date: Fri, 22 Nov 2013 16:11:00 -0700	[thread overview]
Message-ID: <CAFHuXuaqUJO0WUHfUOvvQqL-=hhY5ADrjdbDH=2pnJt+bDH7ig@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0PP-q9cmHKzk5uzRZfLYXpwse4K497Wuuc+7UBrupDd2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]

Wrong patch?  This looks like node.js code for something called txtool.


-- 
Michael


On Fri, Nov 22, 2013 at 1:46 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:

> Trying something new... a [simple] patch sent to the list, for
> discussion.  Seems unlikely to be controversial.  github access is
> temporarily disabled, so this is the best pull request avenue for the
> moment.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc.      https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up
> now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

[-- Attachment #2: Type: text/html, Size: 1926 bytes --]

      reply	other threads:[~2013-11-22 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22 20:46 [Bitcoin-development] [PATCH] bitcoind: whitelist nodes, to prevent them from being banned Jeff Garzik
2013-11-22 23:11 ` Michael Hendricks [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='CAFHuXuaqUJO0WUHfUOvvQqL-=hhY5ADrjdbDH=2pnJt+bDH7ig@mail.gmail.com' \
    --to=michael@ndrix.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /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