From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: replacing ldefs-boot.el
Date: Sat, 26 Nov 2016 12:08:21 +0000 [thread overview]
Message-ID: <874m2ucukq.fsf@russet.org.uk> (raw)
In-Reply-To: <83shqe3fi8.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Nov 2016 08:46:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Fri, 25 Nov 2016 15:11:39 -0500
>>
>> > AFAIU, the suggested method still puts auto-generated files into the
>> > repository.
>>
>> That's right. What it does is to strip down ldefs-boot.el to just the
>> autoloads actually used.
>>
>> The intention is to reduce the rate at which this file changes, and hence
>> reducing the spurious conflicts such a file inevitably causes.
>
> I never had any such conflicts. And since Glenn set up an automated
> job that auto-commits ldefs-boot.el, the problem with changes seems
> all but resolved.
ldefs-boot.el wont cause conflicts per se, because it is not generated
during the build, nor is it versioned -- the situation we had previously
with other autoload files. This change should mean that the necessity
for committing ldefs-boot.el is considerably reduced, since
ldefs-boot-auto.el depends on many fewer files than ldefs-boot.el, and
should mean that diffs are more accurate. It's a small advantage; not
having auto-generated files versioned is perhaps an obsession of mine.
The risk is that it will need more manual intervention. ldefs-boot-auto
is not a complete replacement for ldefs-boot.el. I only know which
autoloaded *functions* have been called. Other forms in autoload are not
captured and have been added manually
(defvar warning-series nil)
(defvar electric-pair-text-pairs '((34 . 34)))
both of which turn out (perhaps surprisingly) to be necessary for
bootstrap. My plan would be to code these dependencies out.
Phil
next prev parent reply other threads:[~2016-11-26 12:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 17:46 replacing ldefs-boot.el Phillip Lord
2016-11-20 19:23 ` Eli Zaretskii
2016-11-20 21:28 ` Phillip Lord
2016-11-21 3:27 ` Eli Zaretskii
2016-11-21 22:03 ` Phillip Lord
2016-11-25 11:23 ` Phillip Lord
2016-11-25 13:28 ` Eli Zaretskii
2016-11-25 18:10 ` Paul Eggert
2016-11-25 19:31 ` Eli Zaretskii
2016-11-25 20:11 ` Stefan Monnier
2016-11-26 6:46 ` Eli Zaretskii
2016-11-26 12:08 ` Phillip Lord [this message]
2016-11-25 21:34 ` Phillip Lord
2016-11-25 23:18 ` Óscar Fuentes
2016-11-26 20:59 ` Phillip Lord
2016-11-27 20:14 ` Nicolas Petton
2016-11-25 21:11 ` Noam Postavsky
2016-11-25 21:57 ` Phillip Lord
2016-11-26 5:34 ` Noam Postavsky
2016-11-26 12:19 ` Phillip Lord
2016-11-27 23:04 ` Noam Postavsky
2016-11-29 14:57 ` Phillip Lord
2016-11-27 21:19 ` Phillip Lord
2016-12-13 12:17 ` Phillip Lord
2016-12-13 14:02 ` Noam Postavsky
2016-12-14 11:53 ` Phillip Lord
2016-12-13 14:58 ` John Wiegley
2016-12-13 16:08 ` Eli Zaretskii
2016-12-14 12:00 ` Phillip Lord
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=874m2ucukq.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).