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 18:25:07 +0300 [thread overview]
Message-ID: <83eg4qbgrw.fsf@gnu.org> (raw)
In-Reply-To: <b4d1ddcd-1ba9-ef27-59a6-5abf317bb7c5@cs.ucla.edu> (message from Paul Eggert on Sat, 10 Sep 2016 19:16:39 -0700)
> Cc: dmantipov@yandex.ru, 23904-done@debbugs.gnu.org, sbaugh@catern.com,
> kieran@kcolford.com
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sat, 10 Sep 2016 19:16:39 -0700
>
>
> [1:text/plain Hide]
>
> I looked into this a bit more, and it appears that there's little point to
> giving the user an option to clone or not clone when copying files, as the
> cloning (or not cloning) can occur anyway.
>
> We plan to release a coreutils version soon and to change the default to clone
> after the release. For Emacs master the next release is far away, so there is
> plenty of time to try out the FICLONE performance improvement. I installed the
> attached two patches and am marking this bug report as done.
The first patch is fine with me.
> The second patch merely updates the documentation to discuss the issue; it is
> logically independent of the first patch, since the issue can occur both with
> and without the first patch.
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.
next prev parent reply other threads:[~2016-09-11 15:25 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 [this message]
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=83eg4qbgrw.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).