From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@catern.com, kieran@kcolford.com, dmantipov@yandex.ru,
23904@debbugs.gnu.org
Subject: bug#23904: Btrfs clone support in copy operations
Date: Wed, 6 Jul 2016 17:08:33 +0200 [thread overview]
Message-ID: <577D1EF1.5020401@cs.ucla.edu> (raw)
In-Reply-To: <83oa6an794.fsf@gnu.org>
On 07/06/2016 04:58 PM, Eli Zaretskii wrote:
> are we sure users will always want this
> unconditionally, completely out of their control? Does 'cp' from
> Coreutils do the same unconditionally, for example?
No, coreutils cp has an option. As I recall it was put in soon after the
btrfs feature was added, and we were worried about bugs in btrfs. This
was several years ago. We're thinking of making cloning the default in
cp (on systems that support it) but haven't gotten around to it.
We could add another optional argument to copy-file as well, if there's
a significant need. I would omit such an option at first, though, as
that's simpler.
next prev parent reply other threads:[~2016-07-06 15:08 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 [this message]
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
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=577D1EF1.5020401@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=23904@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--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).