From: David Bremner <david@tethera.net>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: emacs: reply subject sanitization
Date: Wed, 27 Sep 2017 08:20:56 -0300 [thread overview]
Message-ID: <87poac4cbr.fsf@tethera.net> (raw)
In-Reply-To: <20170926182608.30115-1-jani@nikula.org>
Jani Nikula <jani@nikula.org> writes:
> v2 of id:20170915155716.19597-1-jani@nikula.org, now with test.
>
> BR,
> Jani.
pushed.
d
prev parent reply other threads:[~2017-09-27 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 18:26 emacs: reply subject sanitization Jani Nikula
2017-09-26 18:26 ` [PATCH 1/2] test: add emacs reply test for subjects with TAB Jani Nikula
2017-09-26 18:26 ` [PATCH 2/2] emacs: sanitize subject in replies Jani Nikula
2017-09-26 20:56 ` emacs: reply subject sanitization David Edmondson
2017-09-27 11:20 ` David Bremner [this message]
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poac4cbr.fsf@tethera.net \
--to=david@tethera.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).