From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: sbaugh@catern.com, kieran@kcolford.com, dmantipov@yandex.ru,
23904@debbugs.gnu.org
Subject: bug#23904: Btrfs clone support in copy operations
Date: Sun, 11 Sep 2016 22:20:22 +0300 [thread overview]
Message-ID: <83sht69rbd.fsf@gnu.org> (raw)
In-Reply-To: <a3822de9-ad72-260e-cf50-3e49418629b2@cs.ucla.edu> (message from Paul Eggert on Sun, 11 Sep 2016 10:17:17 -0700)
> Cc: dmantipov@yandex.ru, 23904@debbugs.gnu.org, sbaugh@catern.com,
> kieran@kcolford.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 11 Sep 2016 10:17:17 -0700
>
> Eli Zaretskii wrote:
> > I wonder why we need that text in the manual, it doesn't seem to
> > provide any useful actionable info, just general description of an
> > issue.
>
> The intent is to say that Emacs does not guarantee that its changes to files
> might not survive power outages and the like. The new section briefly suggests
> actions to take if this is of concern. Feel free to remove this stuff if you
> think it so obvious or out-of-scope that it should not be in the manual.
Does anyone else see this text as useful? I'm not going to remove it
if someone might find it helpful.
next prev parent reply other threads:[~2016-09-11 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1467745602.28158.17.camel@kcolford.com>
2016-07-06 0:49 ` bug#23904: Btrfs clone support in copy operations Paul Eggert
2016-07-06 2:45 ` Dmitry Antipov
2016-07-06 5:52 ` Helmut Eller
2016-07-06 11:48 ` Paul Eggert
2016-07-06 14:58 ` Eli Zaretskii
2016-07-06 15:08 ` Paul Eggert
2016-07-06 15:26 ` Eli Zaretskii
2016-07-06 17:32 ` Paul Eggert
2016-09-11 2:16 ` Paul Eggert
2016-09-11 15:25 ` Eli Zaretskii
2016-09-11 17:17 ` Paul Eggert
2016-09-11 19:20 ` Eli Zaretskii [this message]
2016-09-11 22:44 ` Paul Eggert
2016-09-12 2:35 ` 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=83sht69rbd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23904@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=kieran@kcolford.com \
--cc=sbaugh@catern.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 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).