Re: Commitfest: patches Ready for Committer

<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Mon, Oct 6, 2014 at 10:53 PM, Tom Lane
<spandir="ltr"><<a href="mailto:tgl@sss.pgh.pa.us" target="_blank">tgl@sss.pgh.pa.us</a>></span> wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The
levenshtein-distancethingy seems to still be a topic of debate<br /> as well, both as to how we're going to refactor
thecode and as to<br /> what the exact hinting rules ought to be.  If some committer wants<br /> to take charge of it
andresolve those issues, fine; but I don't want<br /> to see it done by just blindly committing whatever the last
submitted<br/> version was.<br /></blockquote></div><br />My 2c. I imagine that in this case the consensus is going to
befirst:<br /></div><div class="gmail_extra">- Move a minimum of the core functions of fuzzystrmatch and rename them
(str_distance?)<br/></div><div class="gmail_extra">- Do not dump fuzzystrmatch and have the levenshtein call those
functions<br/></div><div class="gmail_extra">In any case levenshtein code needs a careful refactoring and some
additionalthoughts first before the hint code is touched.<br /></div><div class="gmail_extra">Regards.<br /></div><div
class="gmail_extra">--<br />Michael<br /></div></div>