Dear committers,
I filed recently the HARMONY-1573, -1650, -1651, -1654 issues with the
suggested patches.
So, to avoid redoubling efforts or superposition of commits because of delay
could somebody take them under a control to estimate and apply if it is
necessary?
All the more, the 1650
Serguei Zapreyev wrote:
Dear committers,
I filed recently the HARMONY-1573, -1650, -1651, -1654 issues with the
suggested patches.
I was looking at 1573 last night, but was too tired to follow the
instructions :) (Take the third attachment, combine with the first, to
produce the second
2006/10/3, Serguei Zapreyev [EMAIL PROTECTED]:
Dear committers,
I filed recently the HARMONY-1573, -1650, -1651, -1654 issues with the
suggested patches.
So, to avoid redoubling efforts or superposition of commits because of delay
could somebody take them under a control to estimate and
On 10/3/06, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
Serguei Zapreyev wrote:
Dear committers,
I filed recently the HARMONY-1573, -1650, -1651, -1654 issues with the
suggested patches.
I was looking at 1573 last night, but was too tired to follow the
instructions :) (Take the third
On 10/3/06, Alexey Varlamov [EMAIL PROTECTED] wrote:
2006/10/3, Serguei Zapreyev [EMAIL PROTECTED]:
Dear committers,
I filed recently the HARMONY-1573, -1650, -1651, -1654 issues with the
suggested patches.
So, to avoid redoubling efforts or superposition of commits because of
delay
I tend to agree. I think that it's a good idea to consider for the
future, but right now, if the fixes help stabilize, great. I think that
stabilization is key right now.
geir
Serguei Zapreyev wrote:
On 10/3/06, Alexey Varlamov [EMAIL PROTECTED] wrote:
2006/10/3, Serguei Zapreyev [EMAIL
Sure, this can wait - say, until classlib tests 100% pass on DRLVM, -
just to let current pace of major changes slow down.
Other than that, I see no compelling reasons to maintain duplicate
impl in DRLVM.
And you bet the reference impl in classlib is mature enough to not
affect VM stability ;)
