Hi Rüdiger, > there always may be special cases which cannot be detected automatically. > Image f.e. on your CWS you removed a header. With m209's hedaburemove01 > that header got moved on the master workspace. CVS does not know about > moving files, so it is a removal and a new file elsewhere. When you now > resync your CWS, your removal of that header is (regarding this single > file) exactly the same thing which meanwhile happened on the MWS. No > reason for the tool to warn or give you an alert, everything is fine. > Nevertheless, the header still exists on it's new location and will > still get delivered from there. So in the end, you change in your CWS > (removing the header) will get lost. The only chance to prevent that is > that you manually check what changes to headers you have done on your > CWS and whether they are still effective after resync. > Cases like the one I described above are allways possible if you move > files around. It in no way restricted to CWS hedaburemove01. What makes > that CWS so special is just that it moved so much files.
Okay, I should have been more clear, sorry. I know that cwsresync cannot detect everything. No automated tool can, and knowing and understanding what you do instead of relying on automatisms is always a good idea :) However, Mathias seemed to suggest that cwsanalyze is able to detect problems which are not detected by cwsresync. At least this is how I understood his mail. And that's the part I don't understand. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
