uploading of new code

Raffaello Giulietti raffaello.giulietti at gmail.com
Thu Apr 19 08:07:36 UTC 2018

On 2018-04-18 19:42, mark.reinhold at oracle.com wrote:
> 2018/4/18 10:27:36 -0700, ecki at zusammenkunft.net:
>> Hello, I would put it on a standalone Git repo on one of the public
>> hosting sites lile.Github, especially for a first discussion
>> (especially good if added JMH comparisions). I would not expect a id
>> quickly/easily and a in-tree webrev could be created by sponsor for
>> final ok.
> For IP clarity, no Oracle engineer will review code that is not posted,
> in some form or another (e-mail, webrev, JIRA), directly to OpenJDK.
> For an initial discussion a patch in e-mail is a fine way to start, even
> for 3,000 lines of code.  Those who care can either read it directly or
> else import it into a local repo for further evaluation.
> - Mark

I already uploaded the code on a GitHub repo last week, just to have it 
published somewhere, but in fact didn't expect this move to be 
recognized as an official delivery to the OpenJDK project, hence never 
advertised the URL.

So I will deliver the exact same code as found on GitHub both to this 
mailing list and to Brian Burkhalter, who is the Oracle engineer in 
charge of [1].

Sorry guys for all these trivia.


[1] https://bugs.openjdk.java.net/browse/JDK-4511638

More information about the core-libs-dev mailing list