| 1 |
On Wed, 16 Dec 2009 23:50:50 +0100 |
| 2 |
Christian Faulhammer <fauli@g.o> wrote: |
| 3 |
> > * Stop committing things that aren't typo fixes without posting them |
| 4 |
> > to this list for review. |
| 5 |
> |
| 6 |
> They are still administrative things reflecting a council decision |
| 7 |
> and setting the repo to official document generation by default. |
| 8 |
|
| 9 |
So? If it's not a typo or trivial formatting fix, you send it out for |
| 10 |
review. Administrative or not, you got it wrong, and you went ahead and |
| 11 |
committed it even after I'd told you to wait until things had settled |
| 12 |
down. |
| 13 |
|
| 14 |
Admit that you screwed up, and make sure it doesn't happen again. Stop |
| 15 |
trying to defend the indefensible. |
| 16 |
|
| 17 |
> Disable kdebuild-1 by default: We had the discussion several times and |
| 18 |
> your only argument now is that there might be consumers of an |
| 19 |
> never-approved EAPI out there. |
| 20 |
|
| 21 |
And, as per procedure, there was not consensus on it so you should not |
| 22 |
have committed it. |
| 23 |
|
| 24 |
> 3 to 4 move: Purely administrative and has been worked on by two |
| 25 |
> people (ulm and myself). |
| 26 |
|
| 27 |
Not purely administrative at all. For starters, you introduced a whole |
| 28 |
load of todo notes into the main document, which we've deliberately not |
| 29 |
been doing. Second, I'd already told you not to commit it until the |
| 30 |
whole "what exactly is in EAPI 3" thing had been sorted out, which |
| 31 |
still hasn't happened -- Portage and the Council are in disagreement, |
| 32 |
and past experience strongly suggests that it isn't necessarily the |
| 33 |
Council that's going to come out on top here... |
| 34 |
|
| 35 |
> Anyway, yes, reviewing is necessary, but if essential changes from my |
| 36 |
> point of view are blocked or stonewalled through that means, I may |
| 37 |
> choose to take action.eas |
| 38 |
|
| 39 |
Your point of view isn't relevant when it's wrong. You're supposed to |
| 40 |
be working with other people here, not committing first and then |
| 41 |
tidying up the mess later. |
| 42 |
|
| 43 |
> > * Don't mess with kdebuild until you're sure that no-one has any |
| 44 |
> > kdebuild packages installed. |
| 45 |
> |
| 46 |
> Don't be too academic. To be sure is not possible. And please don't |
| 47 |
> speak about bridge construction and failure possibilites when you |
| 48 |
> don't know about how an engineering process works. |
| 49 |
|
| 50 |
You could have achieved a high degree of confidence with very little |
| 51 |
difficulty. Instead, this whole mess is spilling over and affecting |
| 52 |
users, and wasting far too much of a lot of people's time for something |
| 53 |
that should have been done without any mess or user impact. |
| 54 |
|
| 55 |
-- |
| 56 |
Ciaran McCreesh |
Archives