From: Ken Raeburn <raeburn@raeburn.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 26459-done@debbugs.gnu.org
Subject: bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull"
Date: Thu, 13 Apr 2017 05:03:35 -0400 [thread overview]
Message-ID: <75777FA6-0342-48EE-958B-40877C3722C5@raeburn.org> (raw)
In-Reply-To: <83fuhciy6u.fsf@gnu.org>
On Apr 13, 2017, at 03:06, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Glenn Morris <rgm@gnu.org>
>> Cc: 26459@debbugs.gnu.org, eggert@cs.ucla.edu, raeburn@raeburn.org
>> Date: Wed, 12 Apr 2017 12:43:01 -0400
>>
>> Eli Zaretskii wrote:
>>
>>>> IIUC 440bafe has made this much slower by defeating the prior "only
>>>> update where needed" aspect of this.
>>>
>>> 440bafe made the rule generate the loaddefs in a temporary file.
>>> Would it help to copy loaddefs.el into loaddefs.tmp before running
>>> batch-update-autoloads?
>>
>> Probably, together with a move-if-change at the end.
>
> Done in 88e0125. Generating loaddefs.el is fast again ;-)
I’m sorry about the inconvenience; doing bootstraps so often I didn’t realize non-bootstraps would be affected so.
next prev parent reply other threads:[~2017-04-13 9:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 8:54 bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Eli Zaretskii
2017-04-12 15:58 ` Glenn Morris
2017-04-12 16:03 ` Eli Zaretskii
2017-04-12 16:43 ` Glenn Morris
2017-04-12 18:09 ` Glenn Morris
2017-04-13 7:06 ` Eli Zaretskii
2017-04-13 9:03 ` Ken Raeburn [this message]
2017-04-13 22:44 ` Paul Eggert
2017-04-14 1:08 ` Glenn Morris
2017-04-14 7:21 ` Eli Zaretskii
2017-04-14 17:08 ` Glenn Morris
2017-04-15 1:25 ` Glenn Morris
2017-04-15 7:30 ` Eli Zaretskii
2017-04-26 18:32 ` Glenn Morris
2017-04-26 20:24 ` Paul Eggert
2017-04-26 20:37 ` bug#26459: 26.0.50; loaddefs.el is regenerated after each 'git pull' Phillip Lord
2017-04-26 20:47 ` bug#26459: 26.0.50; loaddefs.el is regenerated after each "git pull" Glenn Morris
2017-04-12 21:37 ` Paul Eggert
2017-04-13 7:09 ` Eli Zaretskii
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=75777FA6-0342-48EE-958B-40877C3722C5@raeburn.org \
--to=raeburn@raeburn.org \
--cc=26459-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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).