| 1 |
On 10/30/06, Jason Wever <weeve@g.o> wrote: |
| 2 |
> Please triple check what you want to commit and verify that you don't do |
| 3 |
> any of the following (which are punishable by death): |
| 4 |
> |
| 5 |
> 1) remove the last ebuild that is keyworded for a given arch, especially |
| 6 |
> when resulting in broken dependencies. |
| 7 |
> |
| 8 |
> 2) remove the last stable ebuild for an architecture |
| 9 |
> |
| 10 |
> 3) remove the last testing ebuild for an architecture when there is no |
| 11 |
> stable ebuild available after the removal |
| 12 |
> |
| 13 |
> Consider yourself warned. Violation of any of these will cause the |
| 14 |
> jforman death goat squad to be dispatched to your location for a discreet |
| 15 |
> hit. For repeat offenders, public executions will be had, with Spanky |
| 16 |
> hosting. |
| 17 |
|
| 18 |
1) Would it be a good idea for repoman to detect these when scanning |
| 19 |
for QA issues ? |
| 20 |
|
| 21 |
2) Would it be a good idea for repoman to alert QA (and possibly the |
| 22 |
jforman death goat squad) in real time when a dev commits such |
| 23 |
violations (and others) ? This could enable other devs to act right |
| 24 |
away and avoid havoc to spread too far. |
| 25 |
|
| 26 |
Denis. |
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives