emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#23904: closed (Btrfs clone support in copy operati


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#23904: closed (Btrfs clone support in copy operations)
Date: Sun, 11 Sep 2016 02:17:02 +0000

Your message dated Sat, 10 Sep 2016 19:16:39 -0700
with message-id <address@hidden>
and subject line Re: bug#23904: Btrfs clone support in copy operations
has caused the debbugs.gnu.org bug report #23904,
regarding Btrfs clone support in copy operations
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23904: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23904
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Re: Btrfs clone support in copy operations Date: Wed, 6 Jul 2016 02:49:12 +0200 User-agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
Tags: patch

The attached proposed patch to Emacs master builds on a suggestion by Kieran Colford. Kieran, can you please comment on its two FIXMEs?

Attachment: 0001-copy-file-now-uses-GNU-Linux-file-cloning.patch
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: bug#23904: Btrfs clone support in copy operations Date: Sat, 10 Sep 2016 19:16:39 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 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 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.

Attachment: 0001-copy-file-now-uses-GNU-Linux-file-cloning.patch
Description: Text Data

Attachment: 0002-Document-file-synchronization-issues.patch
Description: Text Data


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]