When to submit regression in a PR

[Mark Felder]

On Fri, Jun 21, 2013, at 2:42, Aymeric Mansoux wrote:
> 
> My question therefore is: while I will mention these problems upstream,
> should I also make the PR? Contact the port maintainer directly? 
> I understand it is not FreeBSD specific (same issue on Debian Sid)
> however it really make the current port unusable for those working on
> laptops and those needing to input characters only reachable with the
> compose key.
>

It's probably a good idea to open a PR and let the port maintainer know,
but we really need to have upstream to fix it. FreeBSD discourages doing
custom "development" in the ports tree, so even if you could whip up a
patch to fix it we would prefer that it get committed upstream and the
port updated to pull the new version rather than have the port committer
include a custom patch with the port.