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 sales@march-hare.com.
> -----Original Message----- > From: Craig Graham [mailto:craig at twolips-translations.co.uk] > Sent: Tuesday, March 04, 2003 12:13 PM > > Ian Epperson wrote: > > > Any help or insight would be welcome. > > I've not been using CVS for long, but I've used VB6 with > SourceSafe for some > time. I've found a few times that I've made a mod to a file and then > committed it without actually saving the file to disk- hence > a few times > I've lost minor changes and had to re-do them. If you're > working in an IDE > that allows you to compile and test code on the fly rather > than saving and > explicitly compiling, you may be encountering a similar niggle. Considered that possibility. Immediately after making the change, I saved, compiled, closed, committed the file. When co-worker mentioned that the change wasn't present, I re-opened the file and found the change missing. Now, if I made the change, missed the save, it would have compiled (lousy IDE), but wouldn't have closed without warning, wouldn't have shown the file changed or allowed me to commit. If I missed the close, double-clicking the file (in this IDE) would show me the in-memory version - with my routine intact - which it didn't. Immediately after this happened, I retraced my steps, and questioned my memory of each one. I'm CERTAIN I made the change, I'm fairly certain I saved, compiled and closed. I'm CERTAIN I committed the file and I'm CERTAIN the change disappeared - I have logs to show the last two. If I left off saving or closing, the results I had would be different (warnings, or code NOT gone).