all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: stefankangas@gmail.com, 58224@debbugs.gnu.org
Subject: bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file"
Date: Sun, 02 Oct 2022 08:59:16 +0300	[thread overview]
Message-ID: <83r0zqahqj.fsf@gnu.org> (raw)
In-Reply-To: <YziuAkFkqtHtu+HZ@ACM> (message from Alan Mackenzie on Sat, 1 Oct 2022 21:15:46 +0000)

> Date: Sat, 1 Oct 2022 21:15:46 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, 58224@debbugs.gnu.org, acm@muc.de
> From: Alan Mackenzie <acm@muc.de>
> 
> I've hacked a quick fix together.  The idea is to give the variable
> force-load-messages an extra possibility, 'never.  This suppresses the
> messages we want to suppress.

Instead of inventing a new value that overrides the non-nil value, why
not simply reset the variable to nil?





  reply	other threads:[~2022-10-02  5:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 14:15 bug#58224: 29.0.50; "make bootstrap" spuriously warns: "comp.el newer than byte-compiled file" Stefan Kangas
2022-10-01 14:29 ` Lars Ingebrigtsen
2022-10-01 14:50 ` Eli Zaretskii
2022-10-01 16:10   ` Stefan Kangas
2022-10-01 18:11     ` Alan Mackenzie
2022-10-01 21:15       ` Alan Mackenzie
2022-10-02  5:59         ` Eli Zaretskii [this message]
2022-10-02 10:43           ` Alan Mackenzie
2022-10-02 11:04             ` Eli Zaretskii
2022-10-02 11:32               ` Alan Mackenzie
2022-10-02 15:38               ` Alan Mackenzie
2022-10-02 15:54                 ` Eli Zaretskii
2022-10-02 16:46                   ` Alan Mackenzie
2022-10-02 17:07                     ` Eli Zaretskii
2022-10-02 20:37                       ` Alan Mackenzie
2022-10-02 21:29                         ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r0zqahqj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58224@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=stefankangas@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.