There are like 3 branches so the intent is to clean them all up on a single branch and then merge that branch into trunk when the time is right.
About merging with coverage its probably good if we keep each other in the loop so we can sync up regularly. Quoting Bryce L Nordgren <[EMAIL PROTECTED]>: > > > [EMAIL PROTECTED] wrote on 01/30/2006 > 03:56:25 PM: > > > Sounds good to me. At the same time i would like to create a branch > for > > the expression / feature model work. > > I thought there was already a branch for that? > > In any case, I need to try and ensure that the feature model work is > merged > into coverage_branch regularly. It will ease things down the road > when the > two branches are merged separately onto trunk. > > Bryce > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ---------------------------------------------------------- This mail sent through IMP: https://webmail.limegroup.com/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
