cursive option.

       --perms, -p
              This  option  causes  the  receiving rsync to set the destination
              permissions to be the same as the source permissions.  (See  also
              the --chmod option for a way to modify what rsync considers to be
              the source permissions.)

              When this option is off, permissions are set as follows:

              o      Existing  files (including updated files) retain their ex‐
                     isting  permissions,  though  the  --executability  option
                     might change just the execute permission for the file.

              o      New  files  get  their "normal" permission bits set to the
                     source file’s permissions masked with the receiving direc‐
                     tory’s default permissions (either the receiving process’s
                     umask, or the permissions specified  via  the  destination
                     directory’s  default  ACL),  and  their special permission
                     bits disabled except in the case where a new directory in‐
                     herits a setgid bit from its parent directory.

              Thus, when --perms and --executability are both disabled, rsync’s
              behavior is the same as that of other file‐copy  utilities,  such
              as cp(1) and tar(1).

              In  summary:  to  give  destination  files (both old and new) the
              source permissions, use --perms.  To give new files the  destina‐
              tion‐default   permissions  (while  leaving  existing  files  un‐
              changed), make sure that  the  --perms  option  is  off  and  use
              --chmod=ugo=rwX  (which  ensures that all non‐masked bits get en‐
              abled).  If you’d care to make this  latter  behavior  easier  to
              type,  you could define a popt alias for it, such as putting this
              line in the file ~/.popt (the following defines  the  -Z  option,
              and  includes  --no‐g to use the default group of the destination
              dir):

                  rsync alias ‐Z ‐‐no‐p ‐‐no‐g ‐‐chmod=ugo=rwX

              You could then use this new option in a command such as this one:

                  rsync ‐avZ src/ dest/

              (Caveat: make sure that -a does not follow -Z, or it will  re‐en‐
              able the two --no‐* options mentioned above.)

              The preservation of the destination’s setgid bit on newly‐created
              directories  when --perms is off was added in rsync 2.6.7.  Older
              rsync versions erroneously preserved the three special permission
              bits for newly‐created files when --perms was off, while overrid‐
              ing the destination’s setgid bit setting on a  newly‐created  di‐
              rectory.   Default  ACL observance was added to the ACL patch for
              rsync 2.6.7, so older (or non‐ACL‐enabled) rsyncs use  the  umask
              even  if  default ACLs are present.  (Keep in mind that it is the
              version of the receiving rsync that affects these behaviors.)

       --executability, -E
              This option causes rsync to preserve the executability  (or  non‐
              executability)  of  regular files when --perms is not enabled.  A
              regular file is considered to be executable if at least  one  ’x’
              is  turned  on  in its permissions.  When an existing destination
              file’s executability  differs  from  that  of  the  corresponding
              source file, rsync modifies the destination file’s permissions as
              follows:

              o      To make a file non‐executable, rsync turns off all its ’x’
                     permissions.

              o      To make a file executable, rsync turns on each ’x’ permis‐
                     sion that has a corresponding ’r’ permission enabled.

              If --perms is enabled,