On Wed, Apr 4, 2012 at 13:10, Kapil Thangavelu
<email address hidden> wrote:
>> On 2012/04/04 15:53:23, hazmat wrote:
>> > It seems to be the number one concern regarding the failed MIR.
>> My understanding is that the MIR has been dropped.
> hence the term 'failed'
If it's failed, it's not an argument to have changes going in now.
> ic. we've publicly debated these changes previously last fall,
> i believe your saying that that process needs to be done again?
Sorry, I don't want to frustrate you at all, but try to look from
another perspective: there's a release of Ubuntu *this month*, and we're
rushing with a Go implementation to catch up meanwhile. Then, there's
that massive change set that has seen zero debate in the mailing list. I
hope it's not a surprise that I'm asking more details.
Besides that, where's that previously reviewed document that you
mention? It's not linked from this proposal, and I can't find it
anywhere.
On Wed, Apr 4, 2012 at 13:10, Kapil Thangavelu
<email address hidden> wrote:
>> On 2012/04/04 15:53:23, hazmat wrote:
>> > It seems to be the number one concern regarding the failed MIR.
>> My understanding is that the MIR has been dropped.
> hence the term 'failed'
If it's failed, it's not an argument to have changes going in now.
> ic. we've publicly debated these changes previously last fall,
> i believe your saying that that process needs to be done again?
Sorry, I don't want to frustrate you at all, but try to look from
another perspective: there's a release of Ubuntu *this month*, and we're
rushing with a Go implementation to catch up meanwhile. Then, there's
that massive change set that has seen zero debate in the mailing list. I
hope it's not a surprise that I'm asking more details.
Besides that, where's that previously reviewed document that you
mention? It's not linked from this proposal, and I can't find it
anywhere.
https:/ /codereview. appspot. com/5966076/