My client is using perforce. Like CVS, perforce has the feature where you can create your own branch and check broken code into the branch with out breaking the main line build. When you finally get to a point that you are not going to break the build, you merge your branch with mainline.

Unfortunately, they are not using that branch feature here in that way. Maybe we should be but we are not.

The consequence is that I have been working on some files for a month and they are not getting backup up because they are in my perforce sandbox. They need to be checked in (for the purpose of being backed up) but cannot be because I'm not done with them yet (I don't want to break the build!).

I've never used rsync or unison before. Is there some utiltity or set of commands I can use to recursively descend my directory tree looking for files that are not set the "read only" and copy them and their directory paths to a directory that will be backed up?

It seems like the find command could do this, but I'm not sure how to recreate the directory path under some other directory. I would want to run this daily and only copy files that have changed and are read only.

thanks,
siegfried