Not sure how "keep remote directory up to date" works
I am maintaining a collection at ibiblio.org, and am using winscp to update it. I thought it would be simple to use "keep remote directory up to date" and make sure the local directory only contains files I want to update. So I use BeyondCompare on the local side to keep a mirror site up to date, then I open winscp and switch on "keep remote directory up to date" from that mirror site to the ibiblio ftp site.
My idea was to minimize the amount of data I send to ibiblio each time I update. The trouble is, I have noticed that two particular folders always copy along with ALL their contents, even though they have not been updated for quite a while, and then I noticed that the local and remote file sizes for all my files are different by a random number of bytes for each file, sometimes as much as 200 bytes different, other timers only a few bytes.
Have I misunderstood something here? Why are the file sizes different, and what is the defined behavior of "keep remote directory up to date"???
My idea was to minimize the amount of data I send to ibiblio each time I update. The trouble is, I have noticed that two particular folders always copy along with ALL their contents, even though they have not been updated for quite a while, and then I noticed that the local and remote file sizes for all my files are different by a random number of bytes for each file, sometimes as much as 200 bytes different, other timers only a few bytes.
Have I misunderstood something here? Why are the file sizes different, and what is the defined behavior of "keep remote directory up to date"???