From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: The losing battle of TOFU
Date: Fri, 02 Nov 2012 16:06:00 -0000 [thread overview]
Message-ID: <20121102160617.GA12304@ednor.casa.cgf.cx> (raw)
This isn't really Cygwin-related but I wonder if the battle against TOFU
is well and truly lost. Very few people that I know use it. It's not
even on anyone's radar as something that should be done. Many email
readers default to it.
At NetApp, it's basically the wild west when it comes to quoting style.
Some people use the tried-and-true, "just forward it back along with
email headers". Some people invent their own style, like bracketing
replies with their name. No one puts the quotes first and their replies
after and hardly anyone (besides me) ever trims anything.
Just needed to vent. Not using TOFU makes a lot of sense but I think
the battle is over.
cgf
next reply other threads:[~2012-11-02 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 16:06 Christopher Faylor [this message]
2012-11-02 16:55 ` Adam Dinwoodie
2012-11-02 20:31 ` David Eisner
2012-11-02 20:38 ` Christopher Faylor
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=20121102160617.GA12304@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-talk@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).