Re: git: a643a515f8f0 - main - archivers/libdeflate: Update to 1.24

On Sat, May 31, 2025 at 03:31:53PM +0200, Daniel Engberg wrote:
> On 2025-05-31 14:43, Alexey Dokuchaev wrote:
> > On Sat, May 31, 2025 at 10:36:58AM +0000, Daniel Engberg wrote:
> > > commit a643a515f8f0e6387ac4846270a606ee6e7fb26c
> > > 
> > >    archivers/libdeflate: Update to 1.24
> > >    Changelog: https://github.com/ebiggers/libdeflate/blob/v1.24/NEWS.md
> > >     PR:             283589
> > >     Approved by:    maintainer timeout, 1+ month
> > 
> > I explicitly and several times rejected some of the changes because you
> > repeatedly fail to explain their necessity, there was no timeout.
> > 
> > ./danfe
> 
> Which turned into no progress at all ie timeout.

Absolutely no.

A maintainer timeout is "nobody ever responded".

If the maintainer says "no" or "why do you do this" or "I need time to
check things", there cannot be any timeout.

The fact that you are impatient and want the ports tree to conform to
your own idea of how things should be is absolutely no ground for
maintainer timeout.

Daniel, it is not the first time you have been told this, please stop
invoking maintainer timeout when it suits you hoping nobody will ever
notice that it is not a maintainer timeout..

-- 
Mathieu Arnold