all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: fengli@gmail.com, Thien-Thi Nguyen <ttn@gnuvola.org>,
	emacs-devel@gnu.org
Subject: Re: about the byte-opt.el patch
Date: Fri, 06 Jul 2007 09:03:04 -0400	[thread overview]
Message-ID: <jwvk5td3cvl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ulkdtdfoy.fsf@gnu.org> (Eli Zaretskii's message of "Fri\, 06 Jul 2007 12\:50\:05 +0300")

> Is this change really a good idea?  It defeats the purpose of CVSREAD,
> doesn't it?

Actually, no it doesn't.  "chmod +w" in such a context is more or less like
a "checkout" in RCS, so it's about as close to the right thing as we
can get.  Unless of course the file is *not* changed.

> Perhaps it is better to change autoload.el so that it can
> update even read-only files, and preserve the read-only attribute of a
> file after it's finished updating its autoload cookies.  WDYT?

I think that would be the wrong thing to do since you'd end up with a file
still read-only but modified.


        Stefan

  parent reply	other threads:[~2007-07-06 13:03 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk5td3cvl.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=fengli@gmail.com \
    --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 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.