>I feel bad for the extra work I've caused you guys. > > but we all learned from it...
on the changelog.. yes i tmay have changed, but this is actually good. So we can see until which revision it has changed (either on my hopefully still existing local copy - or by using the sourceforge web-interface and changing the version, e.g. http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/ChangeLog?revision=1158&view=markup http://jump-pilot.svn.sourceforge.net/viewvc/jump-pilot/core/trunk/ChangeLog?revision=1138&view=markup actually it looks like 1138 was last one that contains all changes from Larry ) the question is how to identify in a fast way the files that need to be restored (mhm... probably by using the one written in the changelog?) stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
