patch against manpage

jw schultz jw at pegasys.ws
Thu May 15 18:29:19 EST 2003


On Thu, May 15, 2003 at 10:05:50AM +0200, Paul Slootman wrote:
> Regurgitating an old thread...
> 
> On Wed 12 Mar 2003, jw schultz wrote:
> > > > On Wed, Mar 12, 2003 at 01:27:32PM +0100, Paul Slootman wrote:
> > > > > This is a patch against the manpage to clarify what the --perm option
> > > > > does and does not do.
> > > > 
> > > > If we are going to embellish this description it would be
> > > > good to make it clear that the behavior of rsync in this
> > > > regard is the same as that of cp.
> 
> I've come up with this for the manpage, that should help clear things up
> for just about all people :-) :
> 
> 
> .IP "\fB-p, --perms\fP"
> This option causes rsync to update the permissions of existing destination
> files to be the same as the source files\&.
> Like other file copy utilities new destination files will receive the same
> permissions as their source files with this option\&.
> Without this option, the umask at the receiving end will determine the
> permissions of new files (again, like other file copy utilities)\&.
> 
> 
> I believe that it's accurate, and leaves no room for doubt anywhere (which is
> good for a manpage).

Almost accurate, but it seems awkward.

  This option causes rsync to set destination files to have
  the same the permissions as the source files\&.

  Without this option, new files will have their permissions
  set based on the source files and the umask at the
  receiving end in the same manner as other file copy
  utilities.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw at pegasys.ws

		Remember Cernan and Schmitt



More information about the rsync mailing list