From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Tim Penhey <tim@penhey.net>, Barry Warsaw <barry@python.org>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: [PATCH] vc-bzr.el: avoid stomping files across hardlink branches.
Date: Mon, 10 Nov 2008 21:47:03 -0500 [thread overview]
Message-ID: <jwvk5bb0ykf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <877i7bgq8u.fsf@red-bean.com> (Karl Fogel's message of "Mon, 10 Nov 2008 17:39:29 -0500")
>>> Can we at least have an option to have emacs break hard links on edit?
>> Yes, that would be good. It should work regardless of VC. People using
>> hardlinked trees would know to use it.
> So a variable, something like this?:
> break-hardlinks-on-edit
> "*When saving a file that exists under several names (i.e., has
> multiple hardlinks), break the hardlink associated with
> `buffer-file-name' and write to a new file, so that the other
> instances of the file are not affected by the edits.
> If `buffer-file-name' refers to a symlink, do not break the
> symlink."
> I'm happy to write this, just want to make sure I'm headed down the
> right design path.
That sounds good.
Stefan
next prev parent reply other threads:[~2008-11-11 2:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200810292207.58558.tim@penhey.net>
2008-11-09 3:44 ` [PATCH] vc-bzr.el: avoid stomping files across hardlink branches Karl Fogel
2008-11-09 4:33 ` Miles Bader
2008-11-09 4:44 ` Karl Fogel
2008-11-09 15:03 ` Stefan Monnier
2008-11-10 2:29 ` Tim Penhey
2008-11-10 3:31 ` Stefan Monnier
2008-11-10 22:39 ` Karl Fogel
2008-11-11 2:47 ` Stefan Monnier [this message]
2008-11-29 19:05 ` Karl Fogel
2008-12-01 20:10 ` vc-dir header for bzr (was: Re: [PATCH] vc-bzr.el: avoid stomping files across hardlink branches.) Dan Nicolaescu
2008-12-01 20:30 ` vc-dir header for bzr Karl Fogel
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=jwvk5bb0ykf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=barry@python.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=tim@penhey.net \
/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.