(If an existing destination file has a modification time equal to the source files, it will be updated if the sizes are different.) Note that this does not affect the copying of symlinks or other special files.
Also, a difference of file format between the sender and receiver is always considered to be important enough for an update, no matter what date is on the objects.
Maybe it wouldn't be a big problem though, I'm probably wrong or misunderstanding something. If the source has a newer file then dest, only that file is transfered The issue you mentioned could actually happen, thats true.
Maybe expand on what you're seeing as the platform having 'all its files' synced? But it could even be a feature, not overriding source changed on the dest.
bear in mind that your home dir will have stuff like web browser caches etc that you might want to exclude.well, your q flag is probably suppressing any messages that might tell you what's going on.also, r is redundant, because a implies r (and a bunch of others). try this command, and then take out the P (show progress) if you don't want it.Consequently, I work in a local copy and frequently reports updates all the way down the subdir tree. BUT, since then, it happens EVERY time, whether logged into Windows or not.It's not major—finishes in seconds—but it's still pretty weird. I noticed it was updating unvisited directories again, and I immediately repeated the rsync command. Then I logged into the windows machine while repeating rsync on the Mac. Even if the rsync commands are only a second apart.(If an existing destination file has a modifi‐ cation time equal to the source file’s, it will be updated if the sizes are different.) Note that this does not affect the copying of symlinks or other special files.