From: Miles Bader <miles@gnu.org>
To: Neal Becker <ndbecker2@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Need vc-make-backup-files-when-linked
Date: Wed, 18 Mar 2009 20:59:43 +0900 [thread overview]
Message-ID: <buoy6v3kpn4.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <gpqjf6$5kk$1@ger.gmane.org> (Neal Becker's message of "Wed, 18 Mar 2009 06:47:02 -0400")
Neal Becker <ndbecker2@gmail.com> writes:
> It is commonly recommended to use cp -al to make local clones when using
> mercurial. emacs will not break the hard links when files are edited,
> because vc-make-backup-files is usually nil.
I think the default setting of `vc-make-backup-files' (nil) is quite
dangerous for another reason too: backup files and commits often do not
have the same granularity, and if a user happens to edit for a long
period of time before committing, there's a good chance they'll get
screwed.
This is especially true with source-control systems like CVS or
Subversion that do not allow cheap/undoable local commits, but even for
more modern systems, I don't think Emacs should be making such a
dangerous assumptions (that they commit often, and so do not need Emacs
backup files) about the users' work habits.
Even in the case where a user has commited some changes, I don't think
one can simply assume that the repository contents obviates the need for
backup files -- for instance, I've grovelled through old emacs backup
files trying to find some changes I had made a few days, but erased
before commiting...
-Miles
--
The car has become... an article of dress without which we feel uncertain,
unclad, and incomplete. [Marshall McLuhan, Understanding Media, 1964]
prev parent reply other threads:[~2009-03-18 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 10:47 Need vc-make-backup-files-when-linked Neal Becker
2009-03-18 11:59 ` Miles Bader [this message]
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=buoy6v3kpn4.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ndbecker2@gmail.com \
/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.