[aarch64-port-dev ] Backport patches for 8031818, 8139758 and 8144993

Felix Yang felix.yang at linaro.org
Mon Jun 19 13:38:17 UTC 2017


Clear!  Thanks for the clarification.

On 19 June 2017 at 20:41, Andrew Haley <aph at redhat.com> wrote:

> On 19/06/17 13:16, Felix Yang wrote:
> >     Actually, I am not quite clear about the correct procedure to do
> > backport on jdk8u repo. Please let me know if there is anything wrong I
> am
> > doing.
>
> You just submit them to the -8u list.
>
> >     There are not bugfixing patches, but just performance
> > improvement ones.  So it seems to me that it might be hard or
> > inappropriate for them to go into jdk8u repo, right?
>
> In which case they're inappropriate in aarch64-jdk8u, too.  I can
> think of no reason why stability is less important to AArch64 than to
> the other ports.  Stability is a key component of software quality,
> and I want AArch64 to be of a quality that is just as good as other
> ports.
>
> >     As the jdk8u aarch64 port repo can benefit from these patches in
> > respect of performance, I want this repo to have them.
>
> >     I don't want to keep them in my private repo, but this will
> > surely cause some difference for shared code between jdk8u and jdk8u
> > aarch64 port.
>
> There shouldn't be any differences in shared code between jdk8u and
> jdk8u aarch64 except for critical bugs.  Performance patches could be
> considered if the performance difference was severe and due to a bug,
> but in that case they'd be considered for jdk8u as well.
>
> --
> 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