In article <[EMAIL PROTECTED]>, Stephen Jowitt wrote:
>We develop for Windows and Linux and both systems share source code from
>
>the same repository. Our developers would like to be able to do the
>following:
>
> 1) Write code on windows machine. Compile and test.
> 2) Compile and test the same code on a linux box
> 3) Commit changes to cvs
>
>This would be easy to do if the developers committed the source in
>between
>stages 1 and 2, but they don't want to do that as it is a busy tree and
>would break
>others' builds.
Just commit the changes if the work on one platform. Then check them
out on the other and test. If it breaks, fix it.
It's a good idea to check out after a commit, because you can break
the build even on the platform where it appears to work. For example,
suppose you create a file locally but forget to add it to CVS.
Your copy compiles and runs, but when someone checks it out,
they have a reference to a nonexistent file that only you have.
If the changes are significant and risky, then what you can do is
commit to an experimental branch, and do your multi-platform test
from there.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
