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: Wed, 06 Jul 2016 17:58:15 +0300 [thread overview]
Message-ID: <83oa6an794.fsf@gnu.org> (raw)
In-Reply-To: <577CF00A.80707@cs.ucla.edu> (message from Paul Eggert on Wed, 6 Jul 2016 13:48:26 +0200)
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 6 Jul 2016 13:48:26 +0200
> Cc: sbaugh@catern.com, Kieran Colford <kieran@kcolford.com>
>
> Revised patch attached. Basically untested, since I don't use any file
> systems that support FIOCLONERANGE. The patch still has FIXMEs for what
> happens if the FIOCLONERANGE ioctl is interrupted by a signal, and for a
> good clone chunk size (the patch guesses 1 GiB).
Thanks.
However, I wonder: are we sure users will always want this
unconditionally, completely out of their control? Does 'cp' from
Coreutils do the same unconditionally, for example?
next prev parent reply other threads:[~2016-07-06 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 19:06 Btrfs clone support in copy operations Kieran Colford
2016-07-05 23:39 ` sbaugh
2016-07-06 0:57 ` Paul Eggert
2016-07-06 0:49 ` bug#23904: " 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oa6an794.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 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.