From owner-freebsd-ports@FreeBSD.ORG Wed Jun 4 20:59:55 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7A1E01AC for ; Wed, 4 Jun 2014 20:59:55 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0AE1323F2 for ; Wed, 4 Jun 2014 20:59:54 +0000 (UTC) Received: from spectrum.skysmurf.nl (mail.skysmurf.nl [192.168.42.4] (may be forged)) by spectrum.skysmurf.nl (8.14.7/8.14.7) with SMTP id s54KxoSQ031708 for ; Wed, 4 Jun 2014 22:59:50 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Wed, 04 Jun 2014 22:59:50 +0200 Date: Wed, 4 Jun 2014 22:59:50 +0200 From: "A.J. 'Fonz' van Werven" To: FreeBSD ports mailing list Subject: [games/oneko] Maintainer timeout Message-ID: <20140604205950.GA31633@spectrum.skysmurf.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 20:59:55 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable PR ports/189050 was submitted at 27 April, with a patch for a trivial problem. So far, over a month later, said PR is still stuck on "awaiting maintainer feedback" so I'd say this qualifies as a maintainer timeout. Could a committer at least have a quick look at this? Furthermore, if (and only if) this results in a maintainer reset, I'd be happy to have a look at this port to see if I can stagify it (it hasn't been yet!), whether it needs other fixes and take over maintainership. In that case, I would appreciate being given a few days to do my "homework", so that only one commit is needed. Thanks in advance, AvW --=20 I'm not completely useless, I can be used as a bad example. --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJTj4jGAAoJEAfP7gJTaCe8b+oQALoP2jHp+4l5PYEUwz9oeNyC v4Ka6VymoygQSE8pJgq7B13kkWNbjAUMh6usC+1iwR+YRcoJJg3GjNjkdpROzIXu +oisE/HayiTNTfAOh6upXQNGBrQ/o4iql946nsDsMDP9WjwFhmXOEVDRGSCCOLgl DFM4MT3sd52n6D+zfcfnd0Iqpkg9qTT0lyEb8B1vp+F/AFZ8EO6E+HnBxQJcyIJX d0MdsK0L7WCevXfHIYM8OroQ0h2ncrMeI07/xZ4BjF8B39DpaOatGe6fvylTCVbL KXgz9WI0jnRqud3nEdwZp1wbuNjRzeM9fByWGtKprCJDWRTM550kAOzxaP9iyodg eXjitS57dPjlRfrDT5RxJflPpvFF82lFd6ByynHXHT+aexn7Wzr3EiGv/IIvK0ip 6UgFq6mkwH2KE+PN+9t8q9GvZqUtjB8/6nPGV4cJ1zsL7TqtfZrLhrfPTFKVCgvF wYI41pcKLVMLG3YiCOws0yu3LAoGKLv5nXsftv2ou1DmiH84u7SJayk4tLx0P0xq aWcgsMdfKOcMzFpv/9IioJZ/nHifU3GEvvn7o/rDTzwa5ORnFexXVemLsc77jpz3 kWigZswrGtKx9N/lfs/o2IJgrF8qFkMrYj0e4rotouis2K3nkrtMBtp2p6AmY4e3 zFWLGJ3ZaxwRxg1hNGFM =Tu06 -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ--