From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SPfBB-0005hr-PM for bitcoin-development@lists.sourceforge.net; Wed, 02 May 2012 19:25:37 +0000 X-ACL-Warn: Received: from nm39-vm5.bullet.mail.ne1.yahoo.com ([98.138.229.165]) by sog-mx-3.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1SPfBA-0005HX-Ni for bitcoin-development@lists.sourceforge.net; Wed, 02 May 2012 19:25:37 +0000 Received: from [98.138.90.57] by nm39.bullet.mail.ne1.yahoo.com with NNFMP; 02 May 2012 19:25:31 -0000 Received: from [98.138.89.166] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 02 May 2012 19:25:31 -0000 Received: from [127.0.0.1] by omp1022.mail.ne1.yahoo.com with NNFMP; 02 May 2012 19:25:31 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 59425.91050.bm@omp1022.mail.ne1.yahoo.com Received: (qmail 46451 invoked by uid 60001); 2 May 2012 19:25:30 -0000 X-YMail-OSG: 4OiUN1UVM1klj_.D4tEpj3T1tdyFupELc9H6569YTQVLhF. u6Rn6N_4PMptgciWuD21zp.CaW9zzc6LmUP4V9yw5MsmNyzqSnWDGkXVwXeZ Hyvl6EUl1B4CuUlF7NgSa0I08XrXDnzbiCgKvQkZJ7tb73YINhiuN2uxtY7_ 27JyXcskliYB5qufd7aUwL3F8zkd_O5WjbGALMoAw3_E_QFwCbuM5G81Mj.c Qe139LeVDcuOHgRZDJ6W_RhkFq58fmQaJ9QBMXL8.Pk79l9xHzRXy.i7P6CI Mw9zpYQM.fUj6LCX_KfwnEmF0Jy9f.zxifsfhyYU1l0H5GRSebqKwCLwCr.E Osg9srfVyPbcE.V_4.xhjXaC_M.DOuxutpndTj_qGao.rK_71YDb_KAARTyY EW.sF9orCqQi4N38216DKyPruvp5nxpu8CFnKBrwJcd5gBBaQzLZnR9IBWYd j31qrUWeTqwb9UfTyIhRZCSpYGlY0_Lgshsl4R3jjFIRNZMj3V__P9s9SGT0 9bzDEL.yTkFXsW5TyT46iVTcFi0vHzX8B.jexj7V7X8PstnlzGd6OoAWXW1F 0YoOyArHyNtmFXpThhwzd.mFv2YRJZWdPc4k_efYUIm2ut0dj7KNfqvstphR O_qsOFSOJ Received: from [92.20.156.68] by web121007.mail.ne1.yahoo.com via HTTP; Wed, 02 May 2012 12:25:30 PDT X-Mailer: YahooMailWebService/0.8.118.349524 References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com> <201205020931.01718.luke@dashjr.org> <201205021230.46349.luke@dashjr.org> Message-ID: <1335986730.68336.YahooMailNeo@web121007.mail.ne1.yahoo.com> Date: Wed, 2 May 2012 12:25:30 -0700 (PDT) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: -0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.229.165 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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: 1SPfBA-0005HX-Ni Subject: Re: [Bitcoin-development] new bitcoin.org clients page X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2012 19:25:37 -0000 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 To: grarpamp 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 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