Thank you for developing such a great tool.
If someone wants to update the index they can only choose between -u and -a.
-u rechecks every file and updates the index if the timestamp is modified or files are added, while -a adds only new files.
Can you add a third option to add not just new files but also update all modified files if the timestamp changed, while not rechecking not modified files?
I would assume that not a lot of people completely update the index before doing a backup to a second drive due to the long time it takes and only run it beforehand with -a. This can lead to a scenario where one drive dies and it is unknown whether some of the modified files which have not been updated are corrupted or not. Even if there is no other copy it would be good to at least know that something has been corrupted.
Also what happened to chkbit-py? It redirects to this repo but is still available on pypi.
Thank you for developing such a great tool. If someone wants to update the index they can only choose between -u and -a. -u rechecks every file and updates the index if the timestamp is modified or files are added, while -a adds only new files. Can you add a third option to add not just new files but also update all modified files if the timestamp changed, while not rechecking not modified files? I would assume that not a lot of people completely update the index before doing a backup to a second drive due to the long time it takes and only run it beforehand with -a. This can lead to a scenario where one drive dies and it is unknown whether some of the modified files which have not been updated are corrupted or not. Even if there is no other copy it would be good to at least know that something has been corrupted.
Also what happened to chkbit-py? It redirects to this repo but is still available on pypi.