| 2008-09-18 18:33:40 |
ceg |
description |
Binary package hint: unison
When files gets renamed in replica A, unison shows that the original file is getting deleted in replica B and the renamed file is copied again.
This is particulary unfortunate with picture archives, as they get more often renamed but less often is the file contents changed.
Can't unison queue the cases that look like filedeletions, and at the end, check if they have not just been renamed? And if that is true, just rename the file in the other replica without retransmitting all the files?
Maybe this mechanism could also catch the programmed data loss mentioned under invariants in the documentation (moving a directory with ignored items). |
Binary package hint: unison version 2.27.57
When files gets renamed in replica A, unison shows that the original file is getting deleted in replica B and the renamed file is copied again.
(even though new feature xferbycopying should be true by default)
This is particulary unfortunate with picture archives, as they get more often renamed but less often is the file contents changed.
Can't unison queue the cases that look like filedeletions, and at the end, check if they have not just been renamed? And if that is true, just rename the file in the other replica without retransmitting all the files?
Maybe this mechanism could also catch the programmed data loss mentioned under invariants in the documentation (moving a directory with ignored items). |
|
