I found a bug, at least in the Linux (kernel 2.2.16, CVS 1.10.8) version of CVS. Don't know if it's been reported before. 'cvs diff -N' seems to chop the path portion of newly added files in the diff, so when the result is applied as a patch the new files are always created in the top level directory and not necessarily where the files came from (okay, I used 'cvs diff -uN', but I'm guessing this will always be the case with -N). I edited the path portion of two file sections in a patch by hand and the result applied fine. If anybody thinks it useful I can create a sanity.sh test case for this. I probably won't have time to try and fix myself it for at least a month. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- He who dies with the most toys, is, nonetheless, still dead.