Date: Tue, 10 Apr 2012 06:56:30 -0500 From: Mark Linimon <linimon@lonesome.com> To: Frederic Culot <culot@FreeBSD.org> Cc: ports@FreeBSD.org, cvs-ports@FreeBSD.org, bapt@FreeBSD.org, ports-committers@FreeBSD.org, Pietro Cerutti <gahr@FreeBSD.org> Subject: Re: cvs commit: ports/games/8kingdoms Makefile ports/misc/airoflash Makefile ports/graphics/autopano-sift Makefile ports/x11/avant-window-navigator-xfce4 Makefile ports/lang/boo Makefile ports/x11/cl-clx-sbcl Makefile ports/palm/coldsync ... Message-ID: <20120410115630.GB2456@lonesome.com> In-Reply-To: <20120410114537.GL17460@culot.org> References: <201204092351.q39Npi6F025202@repoman.freebsd.org> <20120410091537.GK98668@gahrfit.gahr.ch> <20120410114537.GL17460@culot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 10, 2012 at 01:45:38PM +0200, Frederic Culot wrote: > To conciliate such a necessary action without hurting the feelings of those > maintainers who despite their work could not update the state of their port in a > timely manner, maybe it would be good to be more verbose in the log of such > commits. Inspired by linimon's emails, something like the following could be > added: I do get some responses from maintainers to those emails, and (except in the cases where the email gets stuck in my mbox) I honor their requests for an extension. OTOH in general I get personal replies and not replies to the list, so people aren't seeing that interaction in public. >From my standpoint, by the time something has been broken for 6 months, the maintainer will have already gotten multiple emails from portsmon. So, I'm going to have to say I'm a little frustrated if I need to send another round of mail even on top of that. mcl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120410115630.GB2456>