-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It was my understanding,
That minor QA violations like this, which affected the sanity of the
tree, were simply added as checks to repoman - which all committing devs
should use. This would (over time) stop new ebuilds of the broken form
appearing, and would flag existing ones as a QA violation. It would
also prevent the mistake from being made in future, and seems the best
and easiest place to stem the flow from.
Whilst not a conspiracy theorist, and whilst also agreeing with the
decision to restrict multiple suffixes of certain types, I am a little
concerned over the haste, announcement to -dev and general backlash
that's been seen here. I'm sure other violations never featured such
dramatic measures. How were they dealt with previously?
Mike 5:)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
iD8DBQFGLnsBu7rWomwgFXoRAt0qAJ0Y1c5pjV7QnCL4J3w02G7s81xVDQCfRcZh
XtbTQNgAo9HV+hxCi3hG0rY=
=BqdS
-----END PGP SIGNATURE-----
--
[EMAIL PROTECTED] mailing list
