Please commit 190341

[Kubilay Kocak]

On 10/07/2014 12:26 AM, Helmut Schneider wrote:
> Hello all,
> 
> is my response still required? The dynamic plist is correct and differs
> only in that way that the old one obvioulsy used reverse sorting order.
> The other 5 differing lines are needed to grant optimal permissions.
> 
> Thanks, Helmut
> 
> --------------------------------------------------
> From: "Kubilay Kocak" <koobs at FreeBSD.org>
> Sent: Wednesday, July 09, 2014 3:31 PM
> To: "Helmut Schneider" <jumper99 at gmx.de>; <freebsd-ports at freebsd.org>
> Cc: "sunpoet Po-Chuan Hsieh" <sunpoet at freebsd.org>
> Subject: Re: Please commit 190341
> 
>> On 9/07/2014 11:29 PM, Kubilay Kocak wrote:
>>> On 9/07/2014 11:08 PM, Helmut Schneider wrote:
>>>> Hi,
>>>>
>>>> an update is available for typo3 and before the port gets messed up
>>>> could someone please commit PR190341?
>>>>
>>>> Thanks, Helmut
>>>>
>>>> _______________________________________________
>>>> freebsd-ports at freebsd.org mailing list
>>>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>>>> To unsubscribe, send any mail to
>>>> "freebsd-ports-unsubscribe at freebsd.org"
>>>>
>>>
>>> Hi Helmut,
>>>
>>> The issue is current in feedback state, waiting for your response on the
>>> difference between the proposed dynamically generated and current static
>>> pkg-plist.
>>>
>>> Please response on the issue in question, which is currently assigned to
>>> sunpoet@ (cc'd)
>>>
>>> Thanks!
>>>
>>
>> Apologies, waiting for "a" response.
>>
>> -- 
>> koobs
>>

Thanks for the quick reply Helmut. Please add your comment to the ticket:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190341

It's also handy to note that bug reports and other change requests can
normally only progress once once questions, issues, concerns or other
considerations have been addressed, and are documented in the issue
tracking system.

Using the mailing lists can be used to get help if you need it, but the
issue tracking system is the *authoritative* source of information on
which changes are made.

One additional tip:

You can 'assure' the correctness of your change to the person(s)
currently assigned to your issue, by attaching the results of a `port
test`, poudriere testport build, or redports build url to the issue.

Hope that helps :)

--
koobs