Futilities/human/fts
< Futilities | human
Jump to navigation
Jump to search
|
FTS: File Tree Sync
|
About
What it does:
- compare files by location; if identical, take no action.
- if a file in A is missing from B (as determined by FTI, then see if there's a file with the same hash elsewhere in the tree.
- If there is, then... uhh... I guess to start with, we'll just want to log these to see what the patterns are, and then I can figure out how to write rules for dealing with the conflict.
- if the same-name file is in both places but the content has changed:
- for now, log this. The obvious resolution is to overwrite the older one, but maybe save it to a journal-folder in case it turns out we wanted to keep the older one or merge them somehow. Maybe I should just go ahead and include that functionality right off the bat. (It seems hella better than the ghastly way the NC client currently handles conflicts...)