From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 38307-done@debbugs.gnu.org, yamaoka@jpl.org
Subject: bug#38307: Lots of important content missing from HTML rendered message
Date: Thu, 21 Nov 2019 23:12:14 +0800 [thread overview]
Message-ID: <87lfs9p8kx.8.fsf@jidanni.org> (raw)
In-Reply-To: <875zjeruvr.8.fsf@jidanni.org>
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> I get a lot more than that when I look at the message you included. Is
LI> the cookie bit included in the text below?
OK, must be the table stuff that you already fixed last time, pending
release on Debian. Thanks. Closing.
(No cookie stuff in the original HTML.)
prev parent reply other threads:[~2019-11-21 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 23:27 bug#38307: Lots of important content missing from HTML rendered message 積丹尼 Dan Jacobson
2019-11-21 13:08 ` Lars Ingebrigtsen
2019-11-21 15:12 ` 積丹尼 Dan Jacobson [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://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=87lfs9p8kx.8.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=38307-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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://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).