unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 48117@debbugs.gnu.org
Subject: bug#48117: 28.0.50; Update of loaddefs.el during normal build is unreliable
Date: Wed, 8 Dec 2021 01:36:25 +0100	[thread overview]
Message-ID: <CADwFkmn4Xk4rFN72q7i5CoOHd5R-DXagUgCfmf--PUkFGYJ9oA@mail.gmail.com> (raw)
In-Reply-To: <87r1ipk323.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 02 May 2021 09:28:04 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> In any case, autoload generation takes a substantial chunk of time --
> especially since it's single-threaded.  Glenn's suggestion to copy over
> ldefs-boot.el (if it's newer) sounds like a good idea to me.  (And I'd
> also like if that file was regenerated more often than once a month...)

If Eli agrees, I'm happy to update ldefs-boot.el more frequently.

Just let me know how often you want it updated and I will make it so.





  parent reply	other threads:[~2021-12-08  0:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30 11:51 bug#48117: 28.0.50; Update of loaddefs.el during normal build is unreliable Eli Zaretskii
2021-04-30 15:01 ` Gregory Heytings
2021-04-30 15:03   ` Eli Zaretskii
2021-04-30 15:47     ` Gregory Heytings
2021-04-30 16:00       ` Eli Zaretskii
2021-04-30 17:32         ` Gregory Heytings
2021-04-30 18:57           ` Eli Zaretskii
2021-04-30 19:08             ` Gregory Heytings
2021-04-30 19:10               ` Eli Zaretskii
2021-04-30 19:20                 ` Gregory Heytings
2021-05-01  0:16                   ` Glenn Morris
2021-05-01  8:09                     ` Gregory Heytings
2021-05-01  8:25                       ` Eli Zaretskii
2021-05-01  9:20                         ` Gregory Heytings
2021-05-01  9:34                           ` Eli Zaretskii
2021-05-01 12:29                             ` Gregory Heytings
2021-05-01 13:00                               ` Eli Zaretskii
2021-04-30 15:22 ` Glenn Morris
2021-04-30 15:38   ` Glenn Morris
2021-04-30 15:51     ` Eli Zaretskii
2021-04-30 15:59     ` Andreas Schwab
2021-04-30 16:03       ` Eli Zaretskii
2021-04-30 16:21         ` Andreas Schwab
2021-04-30 17:54           ` Eli Zaretskii
2021-04-30 17:10       ` Glenn Morris
2021-04-30 17:25     ` Glenn Morris
2021-04-30 17:58       ` Eli Zaretskii
2021-05-02 16:59       ` Glenn Morris
2021-05-02 18:54         ` Eli Zaretskii
2021-05-03  8:41         ` Gregory Heytings
2021-04-30 15:48   ` Eli Zaretskii
2021-05-02  7:28     ` Lars Ingebrigtsen
2021-05-02  7:41       ` Eli Zaretskii
2021-12-08  0:36       ` Stefan Kangas [this message]
2021-12-08  0:40         ` Lars Ingebrigtsen
2021-12-08  3:32         ` Eli Zaretskii
2022-06-05 16:25 ` 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=CADwFkmn4Xk4rFN72q7i5CoOHd5R-DXagUgCfmf--PUkFGYJ9oA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=48117@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rgm@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.
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).