From: Rajeev N via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49754@debbugs.gnu.org
Subject: bug#49754: 27.2.50; mml-preview for multipart/alternative
Date: Wed, 28 Jul 2021 13:21:30 -0400 [thread overview]
Message-ID: <871r7ijqw5.fsf@hm.sivalik.com> (raw)
In-Reply-To: <878s1qa0hi.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 28 Jul 2021 18:04:25 +0200")
[-- Attachment #1: Type: text/html, Size: 476 bytes --]
next prev parent reply other threads:[~2021-07-28 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 12:30 bug#49754: 27.2.50; mml-preview for multipart/alternative Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-28 16:04 ` Lars Ingebrigtsen
2021-07-28 17:21 ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-30 11:31 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r7ijqw5.fsf@hm.sivalik.com \
--to=bug-gnu-emacs@gnu.org \
--cc=49754@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rajeev.jnk@sivalik.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).