Frank Schönheit - Sun Microsystems Germany wrote:
Hi Mathias,
In case you wonder how you can find out which header files you might
have changed: use cwsanalyze to find all changes in your CWS. This is
the best way to avoid problems, it is known that not all possible
combinations of header changes cause errors or alerts in the resync
process.
hmm - can you elaborate on this, please? I'm a little bit shocked to
hear that "it is known that not all possible combinations ... cause ...
alerts". They should, since up 'til now, there is no requirement to do a
cwsanalyze before resyncing - cwsresync alone should do.
Frank,
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.
Rüdiger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
