Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Oct 2017 14:14:36 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 222805] [NEW PORT] dns/dns2blackhole: Malware Prevention through Domain Blocking
Message-ID:  <bug-222805-13-c0QfHvXU5m@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222805-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-222805-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222805

joeb1@a1poweruser.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #186930|0                           |1
        is obsolete|                            |
 Attachment #187134|                            |maintainer-approval+
              Flags|                            |

--- Comment #2 from joeb1@a1poweruser.com ---
Created attachment 187134
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187134&action=
=3Dedit
update shar file

Just a little note to guide your ports work.
In 10 years of submitting ports you are the first one to request Makefile
syntax changes. It's understood that you are empowered to fix these simple
syntax errors on the fly and go ahead and commit the port. Your wasting your
time and mine time cycling such miner fixes back to the submitter. That
portlite is over sensitive and is nothing but a guide, not intended to be u=
sed
in the manner you are using it. You have to execute some judgement, not bli=
ndly
follow some words in some book. Your number of committed ports will rise as=
 you
will have more time to process more ports just by using a little judgement =
and
correcting those simple syntax error your self just like the other committe=
rs
do. This is one of those un-documented rules that experienced commenters
follow. How do you think some of those commenters get such high number of
commits per month? I can guarantee you it's not by cycling every nit syntax
error back to the submitter over and over again. Be assertive, take charge,
correct everything in the port make files that you can so you can commit it.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222805-13-c0QfHvXU5m>