From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Reply calculation
Date: Sat, 25 Jul 2009 15:15:59 -0400 [thread overview]
Message-ID: <1248549271-sup-3371@javelin> (raw)
In-Reply-To: <1248548497-sup-1158@javelin>
After thinking about this some, I think that the only way
to reasonably handle all corner cases is to explicitly ask
the user for a choice in corner cases. Having the default
subtly change based on some non-obvious attributes of an
email is a great way to break muscle memory.
Myself, I have :user in my reply-to.rb hook for now.
Cheers,
Edward
next prev parent reply other threads:[~2009-07-25 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 18:10 Edward Z. Yang
2009-07-25 18:24 ` Edward Z. Yang
2009-07-25 19:03 ` Edward Z. Yang
2009-07-25 19:15 ` Edward Z. Yang [this message]
2009-07-27 16:49 ` William Morgan
2009-07-27 17:09 ` Edward Z. Yang
2009-07-28 15:48 ` William Morgan
2009-07-28 18:34 ` Edward Z. Yang
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=1248549271-sup-3371@javelin \
--to=ezyang@mit.edu \
/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