Date: Sat, 14 Jul 2012 07:55:37 -0700 From: Eitan Adler <lists@eitanadler.com> To: Chris Rees <crees@freebsd.org> Cc: freebsd-ports@freebsd.org, Radim Kolar <hsn@filez.com> Subject: Re: maintainer timeout for FreeBSD commiters Message-ID: <CAF6rxgng6x3jFm9ZCDCUDnnCQrnQBvKezyu3zE2uH=0QrY3u3g@mail.gmail.com> In-Reply-To: <CADLo83_a=qOqTgGQF%2BLSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com> References: <50017C97.3050200@filez.com> <CADLo83_a=qOqTgGQF%2BLSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 July 2012 07:51, Chris Rees <crees@freebsd.org> wrote: > On 14 July 2012 15:05, Radim Kolar <hsn@filez.com> wrote: >> can be maintainer timeout for port patch submissions implemented for people >> which are FREEBSD commiters? I see no reason why they should be exception >> from standard port processing. If they do not care about their ports, they >> should not have power to obstruct other people work. >> >> I have really long term bad experience with that (usually there are stuck >> for 6+ months). I know that it was discussed, but nothing constructive was >> done. >> >> currently i have in queue just these 2: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/166488 >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/167289 > > No-one is exempt from timeouts on ports except secteam and portmgr. > > Have you reminded them by email recently? Apache@ is a team, so it's > a little uncertain where timeouts and approval stands with them. Generally, teams can't timeout. Try poking them a bit and see what they say. :) -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgng6x3jFm9ZCDCUDnnCQrnQBvKezyu3zE2uH=0QrY3u3g>