<br><br><div class="gmail_quote">2010/9/23 Daniel Morissette <span dir="ltr"><<a href="mailto:dmorissette@mapgears.com">dmorissette@mapgears.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Updates have to be committed upstream, ideally by submitting a ticket at<br>
<a href="http://bugzilla.maptools.org/" target="_blank">http://bugzilla.maptools.org/</a> ... eventually I should open the MITAB CVS<br>
repository to more GDAL committers to facilitate this process.<br>
<br>
I have to admit that as new GDAL committers have started making changes<br>
to ogr/ogrsf_fmrts/mitab without making sure the fix is propagated<br>
upstream we've kind of lost control and are in front of a bit of a mess<br>
at the moment.<br>
<br></blockquote><div><br>Daniel,<br><br>Count me as a "new" committer as I've also done some changes in this part, however bug has also been added with these changes at<br><a href="http://trac.osgeo.org/gdal/ticket/3687">http://trac.osgeo.org/gdal/ticket/3687</a> ;-) We may indeed forget to duplicate this into the other BugTracker which would require a more advertised policy to follow. Or we could leave the things as it is, and periodically update all the changes in gdal back to the main stream.<br>
<br>Best regards,<br><br>Tamas<br> <br></div></div><br>