nielash 8c69455c37 sync: don't set dir modtimes if already set ... Before this change, directory modtimes (and metadata) were always synced from src to dst, even if already in sync (i.e. their modtimes already matched.) This potentially required excessive API calls, made logs noisy, and was potentially problematic for backends that create "versions" or otherwise log activity updates when modtime/metadata is updated. After this change, a new DirsEqual function is added to check whether dirs are equal based on a number of factors such as ModifyWindow and sync flags in use. If the dirs are equal, the modtime/metadata update is skipped. For backends that require setDirModTimeAfter, the "after" sync is performed only for dirs that could have been changed by the sync (i.e. dirs containing files that were created/updated.) Note that dir metadata (other than modtime) is not currently considered by DirsEqual, consistent with how object metadata is synced (only when objects are unequal for reasons other than metadata). To sync dir modtimes and metadata unconditionally (the previous behavior), use --ignore-times.		2024-03-07 09:57:11 +00:00
..
golden	sync: don't set dir modtimes if already set	2024-03-07 09:57:11 +00:00
initial
modfiles
scenario.txt	bisync: account for differences in backend features on integration tests - see #5679	2024-01-20 14:50:08 -05:00