You can clone with
HTTPS or Subversion.
Similar to --delete-after, --delay-updates pushes changed files into place after uploading new content, and before deleting removed content. In this way there is a minimal amount of time when a yum or deb repository is in an inconsistent state on disk.
I use my fork of s3cmd to sync my backups to S3. It requires the sync to complete or never at all. Does this my fork/commit work?
See pull request #34.
ryanlim: I like your approach too. rsync uses a upload-to-temp-file-and-rename scheme for all of its files. The trick in the combination of the two is to order the (many) renames such that updated files get renamed last. My patch affects the upload order only. Your patch, if it could take into account setting the rename order, would then be the best of both worlds.
This was merged with #34, so this can be closed.