Date: Wed, 5 May 2021 12:52:44 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Michael Gmelin <freebsd@grem.de>, Neel Chauhan <nc@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Maintainer timeout on textproc/py-markdown update on Bugzilla - safe to commit? Message-ID: <c98148e1-d250-be2a-ffe5-c41afef464a9@FreeBSD.org> In-Reply-To: <3237E5F0-DA2C-4B07-AB7B-4729EA55AD4F@grem.de> References: <67ab40e3dd436ad8fcb2fd1867ac0065@freebsd.org> <3237E5F0-DA2C-4B07-AB7B-4729EA55AD4F@grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/05/2021 6:47 am, Michael Gmelin wrote: > > >> On 4. May 2021, at 22:45, Neel Chauhan <nc@freebsd.org> wrote: >> >> Hi, >> >> There is an update to the port textproc/py-markdown but the maintainer, koobs@ has not responded even when (I believe) it could be committed. >> >> Bugzilla PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239070 >> >> Assuming no dependent ports have an issue with this update, would it be safe to commit this with a maintainer timeout if koobs@ hasn't responded? >> >> I'm asking since I don't want to prematurely commit ports. >> >> This port needs to be updated in order to import GTK+ 4 which in turn needs to update x11-toolkits/pango (which in turn needs this update). >> > > Cc Koobs - looking at the pr, it seems like it was complicated and a lot of other work had to be done first. > > -m > > There's no problem bumping issues and for me at least, I'm usually very clear on explicitly mentioning what needs to happen (even in my absence) for something to land so anyone can do that. I will always approve and unblock well-tested change proposals.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c98148e1-d250-be2a-ffe5-c41afef464a9>