Can someone please look at PR 221573 ?

Bob Eager rde at
Sat Oct 14 09:37:52 UTC 2017

Point taken. I was trying to keep it short to save people's time - or
so I thought.

I will do better next time!

On Fri, 13 Oct 2017 20:16:21 -0700
Kevin Oberman <rkoberman at> wrote:

> On Thu, Oct 12, 2017 at 4:33 PM, Bob Eager <rde at> wrote:
> > It's just coming up to two months, so I thought it might be time to
> > point it out!
> >
> > I know it's a new port, so probably lower priority, but if anyone
> > has time, it would be appreciated.
> >
> > Thanks
> >  
> This message lacks any reference to what port is involved. It even
> lacks a link to the PR (though the number would get me there.
> If you expect to get help from a committer 9which I am not), please
> give them some information so that they have an idea if they are
> likely to have any reason to try dealing with it.
> And, no, this is hardly limited to this post. Seems like over half of
> the requests for a committer to look into a PR lack any reference to
> the port involved, though most do contain a URL.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkoberman at
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to
> "freebsd-ports-unsubscribe at"

More information about the freebsd-ports mailing list