From: Adam Weiss <adam@signal11.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Fwd: Proposed additional options for pruned nodes
Date: Tue, 12 May 2015 17:17:14 -0400 [thread overview]
Message-ID: <CAFVoEQTEdWoqtNLebWtFjUQdGuev=Zs0TWGCj5sRZ2K35ZK4EQ@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0MYSpVBD4VE65LVbADb2daOvE=N83G8F_zDSHy3AQ5DAQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
FYI on behalf of jgarzik...
---------- Forwarded message ----------
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, May 12, 2015 at 4:48 PM
Subject: Re: [Bitcoin-development] Proposed additional options for pruned
nodes
To: Adam Weiss <adam@signal11.com>
Maybe you could forward my response to the list as an FYI?
On Tue, May 12, 2015 at 12:43 PM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> You are the 12th person to report this. It is SF, not bitpay, rewriting
> email headers and breaking authentication.
>
>
> On Tue, May 12, 2015 at 12:40 PM, Adam Weiss <adam@signal11.com> wrote:
>
>> fyi, your email to bitcoin-dev is still generating google spam warnings...
>>
>> --adam
>>
>>
>>
[-- Attachment #2: Type: text/html, Size: 1734 bytes --]
next prev parent reply other threads:[~2015-05-12 21:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANJO25J1WRHtfQLVXUB2s_sjj39pTPWmixAcXNJ3t-5os8RPmQ@mail.gmail.com>
2015-05-12 15:26 ` [Bitcoin-development] Proposed additional options for pruned nodes gabe appleton
2015-05-12 16:05 ` Jeff Garzik
2015-05-12 16:56 ` gabe appleton
2015-05-12 17:16 ` Peter Todd
2015-05-12 18:23 ` Tier Nolan
2015-05-12 19:03 ` Gregory Maxwell
2015-05-12 19:24 ` gabe appleton
2015-05-12 19:38 ` Jeff Garzik
2015-05-12 19:43 ` gabe appleton
2015-05-12 21:30 ` [Bitcoin-development] [Bulk] " gb
2015-05-12 20:02 ` [Bitcoin-development] " Gregory Maxwell
2015-05-12 20:10 ` Jeff Garzik
2015-05-12 20:41 ` gabe appleton
2015-05-12 20:47 ` Gregory Maxwell
[not found] ` <CAFVoEQTdmCSRAy3u26q5oHdfvFEytZDBfQb_fs_qttK15fiRmg@mail.gmail.com>
[not found] ` <CAJHLa0OxxxiVd3JOp8SDvbF8dHj6KHdUNGb9L_GvTe93z3Z8mg@mail.gmail.com>
[not found] ` <CAJHLa0MYSpVBD4VE65LVbADb2daOvE=N83G8F_zDSHy3AQ5DAQ@mail.gmail.com>
2015-05-12 21:17 ` Adam Weiss [this message]
2015-05-12 22:00 ` Tier Nolan
2015-05-12 22:09 ` gabe appleton
2015-05-13 5:19 ` Daniel Kraft
2015-05-13 9:34 ` Tier Nolan
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='CAFVoEQTEdWoqtNLebWtFjUQdGuev=Zs0TWGCj5sRZ2K35ZK4EQ@mail.gmail.com' \
--to=adam@signal11.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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