Derek wrote:
> Doug Barton wrote:
>>> Is the process I follow for an update the same as when submitting a new
>>> port? (ie. shar `find port_dir`)
>>
>> No, you should submit a diff (preferably unified) against the current
>> version of the port as part of your PR.
>>
>
> So, I Googled around for
Doug Barton wrote:
Is the process I follow for an update the same as when submitting a new
port? (ie. shar `find port_dir`)
No, you should submit a diff (preferably unified) against the current
version of the port as part of your PR.
So, I Googled around for the correct process for doing thi
Derek wrote:
> I've done a bunch of updates to the mail/milter-regex port to tidy it
> up, and include support for the RCNG stuff.
It's referred to as rc.d now, since it's not "next generation" anymore. :)
Sounds like you did a lot of homework, just to double check, did you read
the section of the
I've done a bunch of updates to the mail/milter-regex port to tidy it
up, and include support for the RCNG stuff.
I've followed the instructions from:
porters-handbook/porting-testing.html
and also cleaned up any spurious warnings from portlint.
I've been in contact with the person listed as
