Open rpodgorny opened 9 years ago
This bug is still present in the current release (v1.0). Are there any plans to implement the fix in the near future? If not, could you tell me when the diff above is dated so I can match it up with the correct version?
hmmm, i have to admit i've dumped the ancient mail and completely forgot about it. unfortunately, i'll be quite busy during the next month so i can't make any promises.
if you're considering taking a look at this meanwhile, i'll be more than happy. just be sure to start with adding a test to the test suite (test.py) or at least make sure the rename test is already there.
anyway, i've deleted the mail already so i can't date it but looking at the patch, it shouldn't be hard to work it in into the current source (maybe will even be conflict-free).
Does not apply cleanly anymore with the current master (0b35c647a60d22283a04583ac1a29c7d250d9184):
$ git apply fix-excessive-copies.patch
error: patch failed: src/cow.c:130
error: src/cow.c: patch does not apply
error: patch failed: src/findbranch.c:160
error: src/findbranch.c: patch does not apply
error: patch failed: src/findbranch.h:16
error: src/findbranch.h: patch does not apply
error: patch failed: src/unionfs.c:430
error: src/unionfs.c: patch does not apply
so, i've ported to the patch to current version in https://github.com/rpodgorny/unionfs-fuse/tree/issue-25
still, i'm not going to merge it until there's a test proving this works (i've created some basic rename tests in master - feel free to extend).
from ancient email (maybe already fixed):
and