From: brad@heeltoe.com (Brad Parker)
Subject: [Unix-jun72] Change to mail list behaviour
Date: Sun, 04 May 2008 08:47:29 -0400 [thread overview]
Message-ID: <15402.1209905249@mini> (raw)
In-Reply-To: <20080503.125227.1791029143.imp@bsdimp.com>
>: http://www.unicom.com/pw/reply-to-harmful.html
>: http://woozle.org/~neale/papers/reply-to-still-harmful.html
>
>I respectfully disagree.
>
>Religious jihads are like that.
I don't think this is a religious issue. Please read those pages
carefully. It's about normal human behavior and expectations.
I can't tell you how many times I've made the same mistakes
listed in those pages. Many times. Always wit embarrassment.
My mailer has reply and reply-all and I use them consciously every day.
with the new setting I hit reply-all and I generate 2 copies to the
list... so this list becomes unlike all the others I am on.
You may still disagree, but I think there is some sound logic
behind the idea.
-brad
next prev parent reply other threads:[~2008-05-04 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 12:46 Warren Toomey
2008-05-03 18:43 ` John Cowan
2008-05-03 18:52 ` M. Warner Losh
2008-05-04 12:47 ` Brad Parker [this message]
2008-05-04 23:09 ` Cyrille Lefevre
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=15402.1209905249@mini \
--to=brad@heeltoe.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;
as well as URLs for NNTP newsgroup(s).