From richard at imagecraft.com Thu Mar 20 16:56:14 2008 From: richard at imagecraft.com (Richard Man) Date: Thu Mar 20 16:57:49 2008 Subject: [Icc-arm] Eliminating RCS - Message-ID: <200803210057.m2L0vlmj057625@mail.imagecraft.com> At the next major releases, unless there is strong objection, support for the RCS will be removed. I believe it has been broken for a while since some Windows upgrade and most people use their own solution for source code management need. Let me know I am wrong on this. // richard On-line orders, support, and listservers available on web site. [ For technical support on ImageCraft products, please include all previous replies in your msgs. ] From webbra.mlist at verizon.net Sat Mar 22 05:50:27 2008 From: webbra.mlist at verizon.net (Rich Webb) Date: Sat Mar 22 06:50:22 2008 Subject: [Icc-arm] Eliminating RCS In-Reply-To: <200803212001.m2LK11rO089587@mail.imagecraft.com> References: <200803212001.m2LK11rO089587@mail.imagecraft.com> Message-ID: <47E50EA3.2040604@verizon.net> > At the next major releases, unless there is strong objection, support > for the RCS will be removed. I believe it has been broken for a while > since some Windows upgrade and most people use their own solution for > source code management need. I've been using command line rcs and make practically forever across multiple platforms and target processors, typically as an RCS subdir in the project directory. That simplifies archiving a project and its various development trees onto DVD/CD/QIC (once upon a time), although not using a separate server does mean that I have to be careful to actually create backups (good intentions don't count). Us command line dinosaurs probably won't even notice that the integrated rcs is missing... ;-)