> If you have a set of files that are "common" to each side but for whatever reason >the content of which you want to keep separate and "localized" then look into using >--include and --exclude rules or perhaps an exclusion file. The syntax always gets me > and it might take a couple of tries to get the right sequence of element inclusions.
Rene > --__--__-- > > Message: 1 > To: [EMAIL PROTECTED] > From: [EMAIL PROTECTED] > Date: Mon, 15 Oct 2001 13:13:47 -0600 > Subject: (no subject) > > There's nothing in rsync to do that. How about making the files and directories all >belong to another user, set the sticky bit and write for your rsync user on the >directories, unset write for the files, and rsync that way, then chown afterwards? >the > updates to existing files will fail, leaving you only with new. > > Tim Conway > [EMAIL PROTECTED] > 303.682.4917 > Philips Semiconductor - Longmont TC > 1880 Industrial Circle, Suite D > Longmont, CO 80501 > Available via SameTime Connect within Philips > Available as n9hmg on AIM > perl -e 'print pack(nnnnnnnnnnnn, >19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' > "There are some who call me.... Tim?" > > Vipul Ved Prakash <[EMAIL PROTECTED]>@lists.samba.org on 10/13/2001 02:46:38 AM > > Please respond to [EMAIL PROTECTED] > > Sent by: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > cc: (bcc: Tim Conway/LMT/SC/PHILIPS) > Subject: transferring files that don't exist on remote system. > Classification: > > Hi, > > Is there a way to transfer only those files that don't exist on the remote > system? That is, I don't want to update common files even when the local > system has new versions of common files. > > best, > vipul. > > -- > > Vipul Ved Prakash | "I almost died, but I made it, so I'm not so > Software Design Artist | serious about formal-wear anymore." > http://vipul.net/ | -- Gene Boggs > > --__--__-- >
