--- Comment #25 from Carlo Marcelo Arenas BelÃ³n <carenas@???> ---
(In reply to Philip Hazel from comment #24) > (In reply to Zoltan Herczeg from comment #23) > On balance, my preference is not to apply this patch till after the 10.36
fair enough; will rebase it then and upload it here, so people can easily apply
it if needed.
might be worth mentioning in the release notes as a "known issue" of sorts
though to avoid people getting burned by it not being able to find a likely
that will also ensure it gets tested quickly.
> It feels rushed and, given Zoltan's comments above, it is quite
> possible (likely?) that there will be comments and modifications once people
> start using it.
the only part rushed though is the testing, but that might be because we don't
have enough macOS testers/coverage; hopefully this will be improved after this
release since there were participants in this thread from two of the biggest
package managers in macOS AFAIK.
You are receiving this mail because:
You are on the CC list for the bug.
This message was posted to the following mailing lists: