From: grarpamp <grarpamp@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Thu, 3 May 2012 05:06:19 -0400 [thread overview]
Message-ID: <CAD2Ti2_AFj34yZY-7PVc66XbMahr0MwHOMk8AsHQvFncpcee6A@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com>
> "Reply-To" Munging Considered Harmful
> http://www.unicom.com/pw/reply-to-harmful.html
Ok, ok. but only because this reminds me of the
top-posting and formatting advice page that
I can't seem to find right now.
But I'm not munging what my client decides to
put in to/cc on a g reply either :)
next prev parent reply other threads:[~2012-05-03 9:06 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:50 [Bitcoin-development] new bitcoin.org clients page Amir Taaki
2012-04-30 18:23 ` Alan Reiner
2012-04-30 18:31 ` Amir Taaki
2012-04-30 19:51 ` Alan Reiner
2012-05-02 13:22 ` Mike Hearn
2012-05-02 13:30 ` Gregory Maxwell
2012-05-02 13:32 ` Mike Hearn
2012-05-02 13:31 ` Luke-Jr
2012-05-02 16:21 ` grarpamp
2012-05-02 16:30 ` Luke-Jr
2012-05-02 16:58 ` grarpamp
2012-05-02 18:29 ` Jeff Garzik
2012-05-02 19:25 ` Amir Taaki
2012-05-02 19:34 ` Gary Rowe
2012-05-02 19:40 ` Raphael NICOLLE
2012-05-02 19:42 ` Gary Rowe
2012-05-02 19:43 ` Alan Reiner
2012-05-02 19:43 ` Amir Taaki
2012-05-02 19:46 ` Gary Rowe
2012-05-02 19:56 ` Alan Reiner
2012-05-02 20:25 ` Luke-Jr
2012-05-02 20:39 ` Gary Rowe
2012-05-02 19:35 ` Alan Reiner
2012-05-03 9:06 ` grarpamp [this message]
2012-05-02 13:38 ` Gregory Maxwell
2012-05-02 13:42 ` Mike Hearn
2012-05-02 15:01 ` Alan Reiner
2012-05-02 16:53 ` grarpamp
2012-05-03 7:28 ` Andreas Schildbach
2012-05-03 9:24 ` Jorge Timón
2012-05-03 9:53 ` Andreas Schildbach
2012-05-03 10:25 ` Jorge Timón
2012-05-02 23:04 ` Jeff Garzik
2012-05-02 20:41 Jim
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=CAD2Ti2_AFj34yZY-7PVc66XbMahr0MwHOMk8AsHQvFncpcee6A@mail.gmail.com \
--to=grarpamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jgarzik@exmulti.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