Dennis von Ferenczy wrote:
Yes. Get a CVS client for your local machine and do your cvs
commits from there behind the IDE's back. On the CVS server
== web server, use the loginfo hook to keep a reference
sandbox up to date, from which the web site operates.
https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_18.html#SEC158
Thanks for your advice. But what will be the advantage? If I get you right,
then I would have to do a commit every time I want to test the changes in my
scripts, even if I have changed only a single line of code - and even if the
code is buggy. Right now I work locally, have the files mirrored using SSH
(I'm not sure if cvs can use SSH) can immediately try my changes and if
everything works as desired I do a commit. Like this I can always be sure,
that code in the repository is actually code that is working correctly.
It sounds like you use your production environment for testing. Good
configuration management practises dictate that you should never do that.
Configure your local machine to behave the same way as the production
machine. Test on your local machine.
If you do not do this, then sooner or later you *will* crash your
production machine.
--
Jim
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/info-cvs
