[aarch64-port-dev ] Tracking aarch64 downstream backports

Andrew Haley aph at redhat.com
Tue Apr 30 08:00:36 UTC 2019


On 4/29/19 2:06 PM, Andrew Haley wrote:
> On 4/29/19 9:46 AM, Aleksey Shipilev wrote:
>>
>> So... Would you request the new version from ops@, or we just wait
>> for whatever future brings with repository consolidation some
>> (unknown) time later? Either way is fine with me, just want to
>> understand if I should scratch this off my todo list.
> 
> Yes, we should get a new version, I'm just fumbling around trying to
> figure out what to call it. The merged repo is called
> aarch64-port/jdk8u-shenandoah so I'm thinking 8u-aarch64-shenandoah,
> which is a bit long but will have to do.

Ops points out that there is already "11-shenandoah" and
"8-shenandoah". Given that the only active tree in aarch64-port is
http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/ we could use
"8-shenandoah". The problem is that it's a bit confusing, but I can't
see a way to help that.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671


More information about the aarch64-port-dev mailing list