From: Emanuel Berg <incal@dataswamp.org>
To: emacs-tangents@gnu.org
Subject: Re: 2023-02-27 Emacs news
Date: Wed, 01 Mar 2023 21:55:28 +0100 [thread overview]
Message-ID: <87cz5sfayn.fsf@dataswamp.org> (raw)
In-Reply-To: 18b496f7-f23c-67c0-8694-0a71af46848c@yandex.ru
Dmitry Gutov wrote:
> The htmlfontify and etags vulns look a little more
> severe, though.
It's better to just try to identify and fix all issues, big,
small, security, documentation, whatever.
No need to debate if it's important or not, if it's an
improvement and a clear understanding of it as well as how it
can be done - do it.
Is what I think!
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-03-01 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 0:16 2023-02-27 Emacs news Sacha Chua
2023-02-28 1:22 ` Emanuel Berg
2023-02-28 4:04 ` Jean Louis
2023-02-28 14:05 ` Yuri Khan
2023-02-28 18:08 ` Dmitry Gutov
2023-02-28 18:56 ` Yuri Khan
2023-02-28 19:34 ` Dmitry Gutov
2023-03-01 20:55 ` Emanuel Berg [this message]
2023-03-02 10:55 ` Pankaj Jangid
2023-03-03 19:11 ` Akib Azmain Turja
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=87cz5sfayn.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-tangents@gnu.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.
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).