Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to firstname.lastname@example.org.
> From: Alexey Panchenko [mailto:alexey-panchenko at hotmail.ru] > 2) Ideas about save crashdump feature. > > I think it should be configurable. Usually cvs is installed on the > server and nobody sees its dialog "Do you want to save crashdump ?". > In the case above the directory in repository remains locked whilst > this dialog is open. I proposed something similar a couple of months ago; it appears that Tony Hoyle is aggressively uninterested in considering such - especially anything that means he might not see a crashdump, even if it causes considerable inconvenience to users of his software. Best of luck with your proposal, but I don't expect it to be considered. Another topic, then, for list discussion: Would there be any interest in / support for a fork of CVSNT that was intended to implement 'convenience' features such as these, but otherwise track the stable releases of CVSNT? The intention would be to give a broader range of developers commit access to the source, and to use a system of developer voting similar to eg. Tomcat's to tag 'stable' releases. License would be GPL, a CVSNT is now, allowing backporting if Tony wished. Let the flame war^W^Wdiscussion commence! - Peter