From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47105@debbugs.gnu.org, Reza Nikoopour <rnikoopour@gmail.com>
Subject: bug#47105: defface docs
Date: Thu, 18 Mar 2021 08:07:33 +0100 [thread overview]
Message-ID: <87tup9q6ru.fsf@gnus.org> (raw)
In-Reply-To: <83v99wjk9n.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 12 Mar 2021 20:32:04 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> It's the case of "do as I say, not as I do". We cannot always follow
> our own recommendations for some historical reasons.
So I don't think there's anything to fix here, and I'm closing this bug
report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-03-18 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 16:53 bug#47105: defface docs Reza Nikoopour
2021-03-12 18:08 ` Lars Ingebrigtsen
2021-03-12 18:32 ` Eli Zaretskii
2021-03-18 7:07 ` Lars Ingebrigtsen [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=87tup9q6ru.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47105@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rnikoopour@gmail.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).