<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
On 6/7/19, 4:16 PM, Semyon Sadetsky wrote:
<blockquote
cite="mid:d2a80895-77f9-49b1-1cb8-277da04e6224@oracle.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>On 6/7/19 3:14 PM, Philip Race wrote:<br>
</p>
<blockquote type="cite" cite="mid:5CFAE1BA.4040108@oracle.com">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
It is that way in the upstream source so I don't think it is a
problem.<br>
It certainly doesn't affect the legal meaning to have an extra
space.<br>
</blockquote>
<p>It is a legal document, so I suggest it corresponds to the
original up to the symbol to avoid any requests from the right
holder. I just luckily noticed the difference.<br>
</p>
<p>Is it a big deal to correct the text? Can you explain your
point?<br>
</p>
</blockquote>
<br>
I am not sure it needs correcting since it isn't incorrect. I think
it is fine as it is,<br>
but then you wrote yourself above that being the same as the
original is preferable<br>
so I don't understand what you are asking for :<br>
<br>
1) remove the space to be formatted as before, but different than
the original<br>
2) keep the space to be the same as the original <br>
<br>
?<br>
<br>
-phil.<br>
<br>
<blockquote
cite="mid:d2a80895-77f9-49b1-1cb8-277da04e6224@oracle.com"
type="cite">
<p> </p>
<p>--Semyon<br>
</p>
<blockquote type="cite" cite="mid:5CFAE1BA.4040108@oracle.com"> <br>
-phil.<br>
<br>
On 6/7/19, 2:41 PM, <a class="moz-txt-link-abbreviated"
href="mailto:semyon.sadetsky@oracle.com"
moz-do-not-send="true">semyon.sadetsky@oracle.com</a> wrote:
<blockquote
cite="mid:6c169b05-d8ec-f538-4d55-e13deb8571ec@oracle.com"
type="cite">
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
<pre style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">Double space in
20 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
--Semyon </pre>
<br>
<div class="moz-cite-prefix">On 6/7/19 2:15 PM, Phil Race
wrote:<br>
</div>
<blockquote
cite="mid:6155fceb-a0e2-d0e8-0ac5-c1b4ed3bf563@oracle.com"
type="cite">bug : <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://bugs.openjdk.java.net/browse/JDK-8225487">https://bugs.openjdk.java.net/browse/JDK-8225487</a>
<br>
webrev : <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://cr.openjdk.java.net/%7Eprr/8225487/">http://cr.openjdk.java.net/~prr/8225487/</a>
<br>
<br>
A 2016 update to giflib brought in a new source file
openbsd-reallocarray.c <br>
We need attribution for this in the legal markdown file. <br>
This update also changes the file to use the markdown ```
..... ``` convention <br>
instead of <pre> .... </pre> <br>
<br>
-phil. <br>
<br>
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>