| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
It was my understanding, |
| 5 |
That minor QA violations like this, which affected the sanity of the |
| 6 |
tree, were simply added as checks to repoman - which all committing devs |
| 7 |
should use. This would (over time) stop new ebuilds of the broken form |
| 8 |
appearing, and would flag existing ones as a QA violation. It would |
| 9 |
also prevent the mistake from being made in future, and seems the best |
| 10 |
and easiest place to stem the flow from. |
| 11 |
Whilst not a conspiracy theorist, and whilst also agreeing with the |
| 12 |
decision to restrict multiple suffixes of certain types, I am a little |
| 13 |
concerned over the haste, announcement to -dev and general backlash |
| 14 |
that's been seen here. I'm sure other violations never featured such |
| 15 |
dramatic measures. How were they dealt with previously? |
| 16 |
Mike 5:) |
| 17 |
-----BEGIN PGP SIGNATURE----- |
| 18 |
Version: GnuPG v2.0.3 (GNU/Linux) |
| 19 |
|
| 20 |
iD8DBQFGLnsBu7rWomwgFXoRAt0qAJ0Y1c5pjV7QnCL4J3w02G7s81xVDQCfRcZh |
| 21 |
XtbTQNgAo9HV+hxCi3hG0rY= |
| 22 |
=BqdS |
| 23 |
-----END PGP SIGNATURE----- |
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives