From: Amir Taaki <zgenjix@yahoo.com>
To: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Wed, 2 May 2012 12:25:30 -0700 (PDT) [thread overview]
Message-ID: <1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com>
This is like the most annoying thing about email. Often with group emails, we'll be having a conversation then someone will click reply instead of group reply and the convo will go on for a while. Eventually I'll realise the persons are missing and add them back in.
On Yahoo mail (which I use for spam/mailing lists), to do reply all involves clicking a tab, scrolling down and clicking Reply All. Normally I instead go through the steps of reply, delete To, re-enter bitco... select drop down, click send.
Anyone know how to make reply all the default in mutt? And how can I exclude it from re-including my own email when I do a group reply so I don't get the same email again.
----- Original Message -----
From: Jeff Garzik <jgarzik@exmulti.com>
To: grarpamp <grarpamp@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Sent: Wednesday, May 2, 2012 7:29 PM
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
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
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2012-05-02 19:25 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 [this message]
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=1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com \
--to=zgenjix@yahoo.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