[mkgmap-dev] [PATCH v1] Reduce number of cuts in multipolygon processing
From Mark Burton markb at ordern.com on Thu Feb 25 09:37:19 GMT 2010
Hello Marko, > Sure, it is a non-trivial change to the algorithm. What about one week? > If I forget, WanMil please remind me. :-) My rule of thumb for committing non-trivial changes goes along the lines of: if you receive negative reports, either fix the patch or convince the reporter the're doing something wrong! if you receive positive reports, commit the patch when you feel confident that it's received a reasonable amount of testing - the more positive reports you receive, the greater the likelyhood that's it's going to be OK and you can commit sooner rather than later. if you receive no reports, either badger people to try it out or just commit the patch anyway and if it breaks everything that's their fault for not helping with the testing. Something like that. Mark
- Previous message: [mkgmap-dev] [PATCH v1] Reduce number of cuts in multipolygon processing
- Next message: [mkgmap-dev] [PATCH v1] Reduce number of cuts in multipolygon processing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list