Date: Thu, 08 Nov 2012 21:56:22 +0100 From: Marcus von Appen <mva@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r307104 - in head: . x11-toolkits x11-toolkits/motif x11-toolkits/open-motif Message-ID: <20121108215622.Horde.F4tlctjz9kRQnBx2WpiByiA@webmail.df.eu> In-Reply-To: <201211062250.qA6MokKi075971@svn.freebsd.org> References: <201211062250.qA6MokKi075971@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry for you to take the blame below, Cy, this mail is intended for everyone as a short reminder. Cy Schubert <cy@FreeBSD.org>: > Author: cy > Date: Tue Nov 6 22:50:46 2012 > New Revision: 307104 > URL: http://svnweb.freebsd.org/changeset/ports/307104 > > Log: > r307088 broke too much. Rename motif back to open-motif, keeping > the 2.3.3 to > 2.3.4 update and the LGPL 2.1 bit. > > Feature safe: yes I wonder, in which aspect the description of "Feature safe" fails to be understood lately. So for all again from someone not being portmgr@: If you can not guarantee that your commit will have NO impact on other ports (esp. if it is a library or a .mk change), do not commit it. It really is not hard to understand and I am heavily surprised that we seem to be unable to stick to that rule this time. The result of our behaviour seems to be so bad that even a hard freeze had to be announced, because the tree could not be stabilized with the overall commit behaviour. Please understand "Feature safe" as what it actually is intended to mean: "Everything else will still work, if you apply the update". Cheers Marcus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121108215622.Horde.F4tlctjz9kRQnBx2WpiByiA>