Merge ppc port into jdk7u-dev

Lindenmaier, Goetz goetz.lindenmaier at sap.com
Fri Jul 22 08:35:35 UTC 2016


> import a broken port with a ton of patches on top.
Hmm, I would not consider the original port broken, it's what we used
productive for several years before. 
Sure the code that exists now has some issues fixed (7 I think), but that's only 
the normal continuous bugfixing you have in any product.

Best regards,
  Goetz.

> -----Original Message-----
> From: jdk7u-dev [mailto:jdk7u-dev-bounces at openjdk.java.net] On Behalf
> Of Andrew Haley
> Sent: Donnerstag, 21. Juli 2016 18:52
> To: Andrew Hughes <gnu.andrew at redhat.com>
> Cc: jdk7u-dev at openjdk.java.net
> Subject: Re: Merge ppc port into jdk7u-dev
> 
> On 21/07/16 17:29, Andrew Hughes wrote:
> > When backporting changes, you find differences between e.g. 7 and 8,
> > and you need this kind of data mining, from tools like hg annotate, in
> > order to establish why that change exists and whether or not it needs
> > to be kept.
> 
> Yes, but I am still far from convinced that it makes sense to import a
> broken port with a ton of patches on top.  It's a matter of keeping
> the repo reasonably clean.  What is special about the list of bugs
> that you provided?  Why is it OK to merge the changes before that?
> 
> Andrew.



More information about the jdk7u-dev mailing list