summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgrarpamp <grarpamp@gmail.com>2012-05-02 12:58:06 -0400
committerbitcoindev <bitcoindev@gnusha.org>2012-05-02 16:58:18 +0000
commit9a1b7f8f0a0c1707f666fad99b650e9b73cf95a1 (patch)
tree1f1e0577f500fd68b431a6b684ac35da2cc2f294
parentd921e792138756ee29ab83d285f56a6ee2793b54 (diff)
downloadpi-bitcoindev-9a1b7f8f0a0c1707f666fad99b650e9b73cf95a1.tar.gz
pi-bitcoindev-9a1b7f8f0a0c1707f666fad99b650e9b73cf95a1.zip
Re: [Bitcoin-development] new bitcoin.org clients page
-rw-r--r--60/cf23d2055841a28e56ed05aa950852763f247a69
1 files changed, 69 insertions, 0 deletions
diff --git a/60/cf23d2055841a28e56ed05aa950852763f247a b/60/cf23d2055841a28e56ed05aa950852763f247a
new file mode 100644
index 000000000..8e250fca0
--- /dev/null
+++ b/60/cf23d2055841a28e56ed05aa950852763f247a
@@ -0,0 +1,69 @@
+Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
+ helo=mx.sourceforge.net)
+ by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <grarpamp@gmail.com>) id 1SPcsc-0002vd-CC
+ for bitcoin-development@lists.sourceforge.net;
+ Wed, 02 May 2012 16:58:18 +0000
+Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 74.125.82.175 as permitted sender)
+ client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com;
+ helo=mail-we0-f175.google.com;
+Received: from mail-we0-f175.google.com ([74.125.82.175])
+ by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1SPcsW-0007AG-Q7
+ for bitcoin-development@lists.sourceforge.net;
+ Wed, 02 May 2012 16:58:18 +0000
+Received: by wera1 with SMTP id a1so748120wer.34
+ for <bitcoin-development@lists.sourceforge.net>;
+ Wed, 02 May 2012 09:58:06 -0700 (PDT)
+MIME-Version: 1.0
+Received: by 10.216.201.150 with SMTP id b22mr545673weo.103.1335977886726;
+ Wed, 02 May 2012 09:58:06 -0700 (PDT)
+Received: by 10.180.106.229 with HTTP; Wed, 2 May 2012 09:58:06 -0700 (PDT)
+In-Reply-To: <201205021230.46349.luke@dashjr.org>
+References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>
+ <201205020931.01718.luke@dashjr.org>
+ <CAD2Ti2_AUG7zmhwrg1GK9iDOgAh5RNrSEGvJefWCc0Uo=-GQbw@mail.gmail.com>
+ <201205021230.46349.luke@dashjr.org>
+Date: Wed, 2 May 2012 12:58:06 -0400
+Message-ID: <CAD2Ti29NGc7F1_w5VgKm565CXwhrFPZvMx4BgE_5PVbh0SYU5w@mail.gmail.com>
+From: grarpamp <grarpamp@gmail.com>
+To: bitcoin-development@lists.sourceforge.net
+Content-Type: text/plain; charset=UTF-8
+X-Spam-Score: -1.6 (-)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
+ sender-domain
+ 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
+ (grarpamp[at]gmail.com)
+ -0.0 SPF_PASS SPF: sender matches SPF record
+ -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
+ author's domain
+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,
+ not necessarily valid
+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
+X-Headers-End: 1SPcsW-0007AG-Q7
+Subject: Re: [Bitcoin-development] new bitcoin.org clients page
+X-BeenThere: bitcoin-development@lists.sourceforge.net
+X-Mailman-Version: 2.1.9
+Precedence: list
+List-Id: <bitcoin-development.lists.sourceforge.net>
+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
+X-List-Received-Date: Wed, 02 May 2012 16:58:18 -0000
+
+> Try "Reply to All"
+
+That puts the sender in 'to' and list in 'cc',
+which dupes to the sender and eventually
+blows out the to and cc lines as everyone
+chimes in and doesn't trim. 'reply to' solves
+most of that. assuming the list sw can do it.
+
+