Including awt-dev.
David
On 12/06/2015 3:04 AM, Vladimir Kozlov wrote:
First, we should let people know about this. (I don't know client-lib
mailing list).
Fortunately 8075505 is AWT backport bug which was fixed already. 8075505
will not appear in changeset since we use main bug id in backport
changesets. So we don't need to blacklist it for jcheck.
I updated 8075506 to resolved state with linked changeset.
Please, add comment there about bug id.
Regards,
Vladimir
On 6/11/15 2:11 AM, Lindenmaier, Goetz wrote:
Hi Vladimir,
I just figured I have an open bug where I already have submitted the
corresponding
webrev: https://bugs.openjdk.java.net/browse/JDK-8075506
This is because the bugID in the change is wrong, and thus the wrong bug
was closed.
http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/rev/1c471be03faf
I can’t figure what went wrong, as the webrev is fine:
http://cr.openjdk.java.net/~goetz/webrevs/8075506-aixMem/webrev.00/
Probably I messed up the change when editing the reviewers.
Unfortunately, https://bugs.openjdk.java.net/browse/JDK-8075505
is a closed bug, so I can’t tell whether an important issue was lost.
What can I do about this? Could you open 8075505 under a new bugID?
Should I make 8075506 a duplicate of 8075505 and close it?
Sorry for the trouble and best regards,
Goetz.
