Date: Mon, 02 Dec 2013 16:17:00 +0100 From: John Marino <freebsd.contact@marino.st> To: =?ISO-8859-1?Q?Philippe_Aud=E9oud?= <jadawin@FreeBSD.org> Cc: svn-ports-head@freebsd.org, Rene Ladan <rene@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r335281 - in head: . audio audio/gnump3d Message-ID: <529CA46C.4020601@marino.st> In-Reply-To: <20131202151646.GI71618@tuxaco.net> References: <20131202093409.GA71618@tuxaco.net> <529C5F05.6020706@marino.st> <20131202104324.GB71618@tuxaco.net> <529C689B.9050902@marino.st> <20131202131244.GC71618@tuxaco.net> <529C8C1F.7050802@marino.st> <20131202134921.GD71618@tuxaco.net> <529C91F2.6020004@marino.st> <20131202145224.GH71618@tuxaco.net> <529CA16C.2060000@marino.st> <20131202151646.GI71618@tuxaco.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/2/2013 16:16, Philippe Audéoud wrote: > On Mon, 02 Dec 2013, John Marino wrote: >> >> Some of this "power" needs to be clawed back. I will fully support any >> maintainer who is angry at another committer than "fixes" their port >> incorrectly though. I think the benefits of allowing others to fix >> ports-with-listed-maintainers outweighs the negatives by a lot. >> > > Sure but it has to be written. We are both complaining about this point, > maybe we can work together and suggest somes rules/reflexion to > portmgr@. I am not opposed to collaboration at all. It's just that I'm sure the portmgr@ is already well aware of these issues so it's not new territory. If formalizing it would help get the ball rolling, ok, but it would be nice if portmgr was proactive addressing something that's been a known issue far longer than I've been around. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529CA46C.4020601>