Hi Jon, Thanks for pointing this out. Like I said, I'm relatively new to this whole open source experience and I still have a lot to learn and any mentoring is helpful. I've been assuming that the readers of this list are developers who are interested in working out the code and discussing various changes. To this end I think submitting patches is a nice way to go about proposing and discussing a change. Even with write access into the repository, it might be a good habit to continue. In that way developers like myself could submit changes with a large potential affect without jeopardizing the core CVS system and when the change was approved the original author or else someone with CVS write access could merge the changes. CVS branches could also be used for this. Please let me know where my assumptions are incorrect. On another note, has anyone spent any time thinking about or developing a test suite for ensuring that key functionality remains in the system? This may be able to mitigate the affects of changes that developers like myself make to the system. Chris ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
