>Slightly offtopic: >What about doing the review for integration in the Subversion tree >directly and create a fully-automated way to pull-over the tree into a >SCCS reposotory after the review ? AFAIK the prodecure I described in >http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/2006-November/0 01658.html >to move the changed between Subversion trees can be modified to do a >Subversion ---> SCCS transition. > >The advantage would be that we won't hit any problems with >added/removed/missing files and it would save lots of work on your >side...
The point of the exercise is to integrate into ON under SCCS/teamware. Therefore the code review must show the exact differences between ON before and after your project. Not an approximation. Once the review is done the source tree must not be touched again. Any further changes require more review. And I have to chase the latest changes in ON that must also be reflected in the review. For now I'm ignoring those changes but at last count I'm in conflict with 8 files. But as you suggest I need a more automated way of handling these changes so I'm working on that. How much more change is coming? Any more big changes from AT&T? craig
