[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: Two line change in documentation
From:       JC Beyler <jcbeyler () google ! com>
Date:       2018-03-14 17:11:56
Message-ID: CAF9BGBxi7KE71YSTJ1KA8Ny-OvktsUNRFU9nSJ5XeOZBhH92kA () mail ! gmail ! com
[Download RAW message or body]

Thanks Serguei!
Jc


On Wed, Mar 14, 2018 at 10:07 AM serguei.spitsyn@oracle.com <
serguei.spitsyn@oracle.com> wrote:

> Hi Jc,
>
> I forgot to ask you for a patch yesterday.
> Thank you for webrev, it has to be enough as it has a patch in it.
> I'll push it now.
>
> Thanks,
> Serguei
>
>
> On 3/14/18 09:59, JC Beyler wrote:
>
> Hi David and Serguei,
>
> Sorry, I was not sure what would be the process for a small fix like this.
> Did it make sense to make a bug/webrev and all that or not was not clear to
> me. I'll know for next time. Anyway, I assigned the bug to myself, and put
> the fix here:
> http://cr.openjdk.java.net/~jcbeyler/8199561/
>
> Let me know if I need to do anything else,
> Jc
>
>
>
> On Tue, Mar 13, 2018 at 5:56 PM David Holmes <david.holmes@oracle.com>
> wrote:
>
>> On 14/03/2018 7:32 AM, serguei.spitsyn@oracle.com wrote:
>> > Hi Jc,
>> >
>> > Yes, these are typos.
>> > Thank you for fixing them!
>> >
>> > Is it a formal review request (RFR) ?
>> > If so, then a bug number is needed.
>> > I've filed one:
>> >    https://bugs.openjdk.java.net/browse/JDK-8199561
>> >
>> > The fix looks good.
>> > I think, this can be fixed under a trivial fix rule with just one
>> review.
>>
>> I agree. No need for CSR either as these are just obvious typos. :)
>>
>> Thanks,
>> David
>>
>> > I'll sponsor it for you.
>> >
>> > Thanks,
>> > Serguei
>> >
>> >
>> > On 3/13/18 10:37, JC Beyler wrote:
>> >> Hi all,
>> >>
>> >> I saw an error in the SetEventNotificationMode method where the
>> >> parameter is called event_thread but the documentation was referring
>> >> to it as thread. I then went and did a quick scan of the documentation
>> >> and found one type of "couse" instead of "course".
>> >>
>> >> Here is the diff, not sure it was worth doing a webrev for it but let
>> >> me know:
>> >> diff -r 2d1d0c66966b src/hotspot/share/prims/jvmti.xml
>> >> --- a/src/hotspot/share/prims/jvmti.xmlMon Mar 12 14:11:54 2018 -0700
>> >> +++ b/src/hotspot/share/prims/jvmti.xmlTue Mar 13 10:35:03 2018 -0700
>> >> @@ -693,7 +693,7 @@
>> >>      mechanism causes the unload (an unload mechanism is not specified
>> >> in this document)
>> >>      or the library is (in effect) unloaded by the termination of the
>> >> VM whether through
>> >>      normal termination or VM failure, including start-up failure.
>> >> -    Uncontrolled shutdown is, of couse, an exception to this rule.
>> >> +    Uncontrolled shutdown is, of course, an exception to this rule.
>> >>      Note the distinction between this function and the
>> >>      <eventlink id="VMDeath">VM Death event</eventlink>: for the VM
>> >> Death event
>> >>      to be sent, the VM must have run at least to the point of
>> >> initialization and a valid
>> >> @@ -9405,7 +9405,7 @@
>> >>     the event <paramlink id="event_type"></paramlink> will be disabled
>> >>   </constant>
>> >> </constants>
>> >> -If <code>thread</code> is <code>NULL</code>,
>> >> +If <code>event_thread</code> is <code>NULL</code>,
>> >> the event is enabled or disabled globally; otherwise, it is
>> >> enabled or disabled for a particular thread.
>> >> An event is generated for
>> >>
>> >> Thanks,
>> >> Jc
>> >
>>
>
>

[Attachment #3 (text/html)]

<div dir="ltr">Thanks Serguei!<div>Jc</div></div><br><br><div \
class="gmail_quote"><div dir="ltr">On Wed, Mar 14, 2018 at 10:07 AM <a \
href="mailto:serguei.spitsyn@oracle.com">serguei.spitsyn@oracle.com</a> &lt;<a \
href="mailto:serguei.spitsyn@oracle.com">serguei.spitsyn@oracle.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <div class="m_-3831337859530762045moz-cite-prefix">Hi Jc,<br>
      <br>
      I forgot to ask you for a patch yesterday.<br>
      Thank you for webrev, it has to be enough as it has a patch in it.<br>
      I&#39;ll push it now.<br>
      <br>
      Thanks,<br>
      Serguei<br>
      <br>
      <br>
      On 3/14/18 09:59, JC Beyler wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div dir="ltr">Hi David and Serguei,
        <div><br>
        </div>
        <div>Sorry, I was not sure what would be the process for a small
          fix like this. Did it make sense to make a bug/webrev and all
          that or not was not clear to me. I&#39;ll know for next time.
          Anyway, I assigned the bug to myself, and put the fix here:</div>
        <div><a href="http://cr.openjdk.java.net/%7Ejcbeyler/8199561/" \
target="_blank">http://cr.openjdk.java.net/~jcbeyler/8199561/</a><br>  </div>
        <div><br>
        </div>
        <div>Let me know if I need to do anything else,</div>
        <div>Jc</div>
        <div><br>
        </div>
      </div>
      <br>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Tue, Mar 13, 2018 at 5:56 PM David Holmes &lt;<a \
href="mailto:david.holmes@oracle.com" target="_blank">david.holmes@oracle.com</a>&gt; \
wrote:<br>  </div>
        <blockquote class="gmail_quote">On 14/03/2018 7:32 AM, <a \
href="mailto:serguei.spitsyn@oracle.com" \
target="_blank">serguei.spitsyn@oracle.com</a> wrote:<br>  &gt; Hi Jc,<br>
          &gt;<br>
          &gt; Yes, these are typos.<br>
          &gt; Thank you for fixing them!<br>
          &gt;<br>
          &gt; Is it a formal review request (RFR) ?<br>
          &gt; If so, then a bug number is needed.<br>
          &gt; I&#39;ve filed one:<br>
          &gt;      <a href="https://bugs.openjdk.java.net/browse/JDK-8199561" \
rel="noreferrer" target="_blank">https://bugs.openjdk.java.net/browse/JDK-8199561</a><br>
  &gt;<br>
          &gt; The fix looks good.<br>
          &gt; I think, this can be fixed under a trivial fix rule with
          just one review.<br>
          <br>
          I agree. No need for CSR either as these are just obvious
          typos. :)<br>
          <br>
          Thanks,<br>
          David<br>
          <br>
          &gt; I&#39;ll sponsor it for you.<br>
          &gt;<br>
          &gt; Thanks,<br>
          &gt; Serguei<br>
          &gt;<br>
          &gt;<br>
          &gt; On 3/13/18 10:37, JC Beyler wrote:<br>
          &gt;&gt; Hi all,<br>
          &gt;&gt;<br>
          &gt;&gt; I saw an error in the SetEventNotificationMode method
          where the<br>
          &gt;&gt; parameter is called event_thread but the
          documentation was referring<br>
          &gt;&gt; to it as thread. I then went and did a quick scan of
          the documentation<br>
          &gt;&gt; and found one type of &quot;couse&quot; instead of \
&quot;course&quot;.<br>  &gt;&gt;<br>
          &gt;&gt; Here is the diff, not sure it was worth doing a
          webrev for it but let<br>
          &gt;&gt; me know:<br>
          &gt;&gt; diff -r 2d1d0c66966b
          src/hotspot/share/prims/jvmti.xml<br>
          &gt;&gt; --- a/src/hotspot/share/prims/jvmti.xmlMon Mar 12
          14:11:54 2018 -0700<br>
          &gt;&gt; +++ b/src/hotspot/share/prims/jvmti.xmlTue Mar 13
          10:35:03 2018 -0700<br>
          &gt;&gt; @@ -693,7 +693,7 @@<br>
          &gt;&gt;         mechanism causes the unload (an unload mechanism
          is not specified<br>
          &gt;&gt; in this document)<br>
          &gt;&gt;         or the library is (in effect) unloaded by the
          termination of the<br>
          &gt;&gt; VM whether through<br>
          &gt;&gt;         normal termination or VM failure, including
          start-up failure.<br>
          &gt;&gt; -      Uncontrolled shutdown is, of couse, an exception
          to this rule.<br>
          &gt;&gt; +      Uncontrolled shutdown is, of course, an
          exception to this rule.<br>
          &gt;&gt;         Note the distinction between this function and
          the<br>
          &gt;&gt;         &lt;eventlink id=&quot;VMDeath&quot;&gt;VM Death
          event&lt;/eventlink&gt;: for the VM<br>
          &gt;&gt; Death event<br>
          &gt;&gt;         to be sent, the VM must have run at least to the
          point of<br>
          &gt;&gt; initialization and a valid<br>
          &gt;&gt; @@ -9405,7 +9405,7 @@<br>
          &gt;&gt;       the event &lt;paramlink
          id=&quot;event_type&quot;&gt;&lt;/paramlink&gt; will be disabled<br>
          &gt;&gt;    &lt;/constant&gt;<br>
          &gt;&gt; &lt;/constants&gt;<br>
          &gt;&gt; -If &lt;code&gt;thread&lt;/code&gt; is
          &lt;code&gt;NULL&lt;/code&gt;,<br>
          &gt;&gt; +If &lt;code&gt;event_thread&lt;/code&gt; is
          &lt;code&gt;NULL&lt;/code&gt;,<br>
          &gt;&gt; the event is enabled or disabled globally; otherwise,
          it is<br>
          &gt;&gt; enabled or disabled for a particular thread.<br>
          &gt;&gt; An event is generated for<br>
          &gt;&gt;<br>
          &gt;&gt; Thanks,<br>
          &gt;&gt; Jc<br>
          &gt;<br>
        </blockquote>
      </div>
    </blockquote>
    <br>
  </div>

</blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic