unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thien-Thi Nguyen <ttn@gnuvola.org>, emacs-devel@gnu.org
Subject: Re: File-specific autoloads
Date: Fri, 06 Jul 2007 21:32:23 -0400	[thread overview]
Message-ID: <jwvfy410zkt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <u1wflcyca.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 06 Jul 2007 19\:04\:53 +0300")

> Anyway, seeing those "M ps-print.el" lines in the output of "cvs up"
> is extremely annoying, because I'm used to take that as a sign that I
> have uncommitted changes in my sandbox.  It also breaks the principle
> that files that are rewritten locally as part of the build process are
> not kept in CVS.

> So I think this change in its current incarnation is for the worse.
> Maybe if the autoloads were written into files that are not in CVS I'd
> be happier.

Indeed, there's a problem with the current situation.  I have an idea to
solve this problem, I'll install a patch shortly,


        Stefan

  parent reply	other threads:[~2007-07-07  1:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05  0:04 about the byte-opt.el patch Feng Li
2007-07-05 12:54 ` Richard Stallman
2007-07-05 16:19 ` Thien-Thi Nguyen
2007-07-05 17:17   ` Stefan Monnier
2007-07-05 20:46     ` Thien-Thi Nguyen
2007-07-06  9:50       ` Eli Zaretskii
2007-07-06 11:00         ` Thien-Thi Nguyen
2007-07-06 13:03         ` Stefan Monnier
2007-07-06 10:53     ` File-specific autoloads (was: about the byte-opt.el patch) Eli Zaretskii
2007-07-06 14:02       ` File-specific autoloads Thien-Thi Nguyen
2007-07-06 16:04         ` Eli Zaretskii
2007-07-06 18:28           ` Thien-Thi Nguyen
2007-07-07  1:32           ` Stefan Monnier [this message]
2007-07-07 10:16             ` Eli Zaretskii
2007-07-07  4:55           ` Stefan Monnier
2007-07-07 10:43             ` 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=jwvfy410zkt.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ttn@gnuvola.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).