all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: David Bremner <david@tethera.net>, 22213@debbugs.gnu.org
Subject: bug#22213: 24.5; please allow specification or elimination of timestamp in autoloads
Date: Mon, 21 Dec 2015 10:59:55 -0500	[thread overview]
Message-ID: <jwv7fk7g5fg.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <06zix4ab5w.fsf@fencepost.gnu.org> (Glenn Morris's message of "Sun, 20 Dec 2015 19:38:19 -0500")

> A question about the timestamps in loaddefs files:
> Why do we need to store the last modtime for each input file?
> Why can't we just compare current modtime of input file against that of
> the loaddefs file itself? Is there a reason not to trust the latter?

Right, now I remember: for lisp/loaddefs.el I think the timestamps
wouldn't be needed and we could use the file's modtime instead.

But for autoloads.el in general this is not true because of the
existence of entry points such as update-file-autoloads which mean that
the autoloads file may be updated for some of the files it covers rather
than for all of them.


        Stefan





  parent reply	other threads:[~2015-12-21 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 18:52 bug#22213: 24.5; please allow specification or elimination of timestamp in autoloads David Bremner
2015-12-19 19:11 ` Glenn Morris
2015-12-19 19:49   ` David Bremner
2015-12-20  3:39     ` Glenn Morris
2015-12-21  0:38       ` Glenn Morris
2015-12-21  1:54         ` Stefan Monnier
2015-12-21  2:20           ` Glenn Morris
2015-12-21 15:59         ` Stefan Monnier [this message]
2016-01-07  7:42           ` Glenn Morris
2016-01-08  7:41             ` Stefan Monnier
2016-01-08 14:53               ` Drew Adams
2016-05-25 22:37               ` Glenn Morris
2015-12-21 12:28       ` David Bremner
2015-12-20  9:33     ` Philipp Stephani
2015-12-20  9:29 ` Philipp Stephani

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=jwv7fk7g5fg.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=22213@debbugs.gnu.org \
    --cc=david@tethera.net \
    --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 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.