public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@exmulti.com>
To: grarpamp <grarpamp@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Wed, 2 May 2012 14:29:01 -0400	[thread overview]
Message-ID: <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti29NGc7F1_w5VgKm565CXwhrFPZvMx4BgE_5PVbh0SYU5w@mail.gmail.com>

On Wed, May 2, 2012 at 12:58 PM, grarpamp <grarpamp@gmail.com> wrote:
>> 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.

"Reply-To" Munging Considered Harmful
http://www.unicom.com/pw/reply-to-harmful.html



-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com



  reply	other threads:[~2012-05-02 18:29 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 [this message]
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
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=CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com \
    --to=jgarzik@exmulti.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=grarpamp@gmail.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