Submitted JEP: Asynchronous Stack Trace VM API
Bechberger, Johannes
johannes.bechberger at sap.com
Thu Oct 27 20:49:52 UTC 2022
> For IP clarity, could you please also move the demo into the same
sandbox branch? You can place it under src/demo/share for now.
What do you mean with the demo? My demo repository with the modified async-profiler? The async-profiler is Apache 2.0 licensed which should not be a problem (as far I understand it).
Regards
Johannes
From: Mark Reinhold <mark.reinhold at oracle.com>
Date: Thursday, 27. October 2022 at 22:24
To: Bechberger, Johannes <johannes.bechberger at sap.com>
Cc: andrei.pangin at gmail.com <andrei.pangin at gmail.com>, Langer, Christoph <christoph.langer at sap.com>, jaroslav.bachorik at datadoghq.com <jaroslav.bachorik at datadoghq.com>, serviceability-dev at openjdk.org <serviceability-dev at openjdk.org>
Subject: Re: Submitted JEP: Asynchronous Stack Trace VM API
2022/10/11 1:18:19 -0700, johannes.bechberger at sap.com:
> Thanks for your comments. I incorporated them in the updated version
> of the JEP and updated all related repositories that now are
> implemented based on current JDK20 head and async-profiler head. The
> implementation of the JEP now resides in the sandbox repository too.
Thanks, that’s an improvement.
For IP clarity, could you please also move the demo into the same
sandbox branch? You can place it under src/demo/share for now.
I’ll copy-edit the JEP text shortly.
- Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/serviceability-dev/attachments/20221027/3d687c78/attachment-0001.htm>
More information about the serviceability-dev
mailing list