unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Frank Schmitt <ich@Frank-Schmitt.net>
Subject: Re: Fixing the lisp/loaddefs.el situation
Date: Sat, 13 Sep 2003 08:29:02 +0200	[thread overview]
Message-ID: <ufzj1w6a9.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: 874qzhcuqf.fsf@tc-1-100.kawasaki.gol.ne.jp

Miles Bader <miles@gnu.org> writes:

> I've fixed this by renaming `loaddefs.el' to `loaddefs-boot.el', and
> changing lisp/Makefile.in to copy the former from the latter when
> necessary (basically during bootstrap-clean, only if there's no existing
> loaddefs.el, and no emacs binary to build it with).*
[...]
> Does anyone have any objection to this change?

I think this is an excellent idea, I hate it to have dozens of
#loaddefs.el.xxx files in my lisp folder resulting from conflicts when
merging.

Just one question: Will a simple "make" be enough to ensure that new
autoloads are recognized when building?

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.

  reply	other threads:[~2003-09-13  6:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-13  2:01 Fixing the lisp/loaddefs.el situation Miles Bader
2003-09-13  6:29 ` Frank Schmitt [this message]
2003-09-13  7:03 ` David Ponce
2003-09-13 12:52   ` Miles Bader
2003-09-15  6:38 ` Miles Bader
2003-09-22 17:46   ` Eli Zaretskii
2003-09-22 22:50     ` Miles Bader
2003-09-23  6:14       ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15  6:51 David PONCE
2003-09-16  2:23 ` Miles Bader

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=ufzj1w6a9.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    /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).