On 9/7/16 00:45, Dmitry Samersoff wrote:
Serguei,
I'm OK with the fix and OK to be listed as a reviewer.
Thanks, Dmitry!
Serguei
-Dmitry
On 2016-09-07 07:08, serguei.spit...@oracle.com wrote:
Hi Dmitry,
As a sponsor I'm going to push this fix if you are Ok with the fix.
Please, let me
Serguei,
I'm OK with the fix and OK to be listed as a reviewer.
-Dmitry
On 2016-09-07 07:08, serguei.spit...@oracle.com wrote:
> Hi Dmitry,
>
> As a sponsor I'm going to push this fix if you are Ok with the fix.
> Please, let me know if you still have any concerns.
> Also, confirm if you are
Hi Dmitry,
As a sponsor I'm going to push this fix if you are Ok with the fix.
Please, let me know if you still have any concerns.
Also, confirm if you are Ok to be in the list of reviewers.
On 9/5/16 06:46, Dmitry Samersoff wrote:
Yasumasa,
I'll look closely to the fix.
Please, notice:
1.
Hi Dmitry,
I'll look closely to the fix.
Thanks!
1. We typically avoid printing attach error messages on
the target VM side.
My change will not print error message(s) on the target VM side.
Yasumasa
On 2016/09/05 22:46, Dmitry Samersoff wrote:
Yasumasa,
I'll look closely to the
Yasumasa,
I'll look closely to the fix.
Please, notice:
1. We typically avoid printing attach error messages on
the target VM side.
2. We are in RDP1 for jdk9.
http://mail.openjdk.java.net/pipermail/jdk9-dev/2016-August/004777.html
-Dmitry
On 2016-09-05 16:25, Yasumasa Suenaga wrote:
>
PING: Could you review and sponsor it?
http://cr.openjdk.java.net/~ysuenaga/JDK-8164913/webrev.01/
Thanks,
Yasumasa
On 2016/09/01 12:47, Yasumasa Suenaga wrote:
Hi all,
I think RDP1 has been started.
Cannot I fix this?
This problem is that jcmd shows incorrect status when JVMTI
