From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: File-specific autoloads
Date: Fri, 06 Jul 2007 16:02:59 +0200 [thread overview]
Message-ID: <87zm29eijw.fsf@ambire.localdomain> (raw)
In-Reply-To: <ubqepdcr6.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 06 Jul 2007 13\:53\:33 +0300")
() Eli Zaretskii <eliz@gnu.org>
() Fri, 06 Jul 2007 13:53:33 +0300
Because of this change, "cvs up" now shows ps-print.el and
cl-loaddefs.el as modified, which might cause trouble if, say,
ps-print.el is ever modified in the repository.
brief experiments w/ chmod +w; touch; rewrite (random mod plus undo
plus save) -- all do not result in "cvs up" displaying "M filename".
this is w/ CVSREAD=1 and cvs --version 1.11.22. ymmv.
but regardless of cvs version quirks, let's look at the nature of the
changes: autoload processing changes a specified region; programmers
should not change that region manually. i think possible conflict (as
evidenced by a "C" line on "cvs up") is unlikely. any such conflict
would be good to know about.
thi
next prev parent reply other threads:[~2007-07-06 14:02 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 ` Thien-Thi Nguyen [this message]
2007-07-06 16:04 ` File-specific autoloads Eli Zaretskii
2007-07-06 18:28 ` Thien-Thi Nguyen
2007-07-07 1:32 ` Stefan Monnier
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=87zm29eijw.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).