Sorry for sounding dumb... who is the maintainer in this instance? Is it Martin Friebe, the person who raised the original issue? The person who commissioned me was someone else entirely, and I think I got their attention because I bumped the priority level up back in December. They are perfectly satisfied with the patch, but they're only working on i386-win32 and x86_64-win64.
At least from my own preliminary tests, both patches seem to suffice insomuch as my new extensive test, tw34772.pp, passes without incident, although I've only run the full regression suite on my own patch. I marked the issue as "feedback", waiting for Martin Friebe to respond, but nothing yet, so it may be a few days. Gareth aka. Kit On Mon 22/04/19 11:19 , "Jonas Maebe" jo...@freepascal.org sent: On 22/04/2019 08:10, J. Gareth Moreton wrote: > The question is this... what's the policy when there are two vastly > different patches on offer that fix the same bug (and which cannot > really be merged together)? The bounty has already been resolved > separately, so it's just a matter of what gets merged into the FPC trunk. In general, it's up to the maintainer to decide. Jonas _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel [1]">http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel Links: ------ [1] http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
