Hi Chris,
thanks for reviewing - I generated the patches today again so now it
should be ok:
http://cr.openjdk.java.net/~mkos/8029237/copyrights-2012-v02.patch
http://cr.openjdk.java.net/~mkos/8029237/copyrights-2013-v02.patch
Could you push it for me? I have no rights for jdk8.
I suppose the
Miran,
This bug has not been approved for JDK 8, in fact it was considered and
rejected. The fix should be pushed to jdk9/dev, if applicable. If the
patches apply cleanly I can push it for you. Do you want it in JDK 9?
-Chris.
On 24/01/14 09:41, Miroslav Kos wrote:
Hi Chris,
thanks for
Hi Chris,
I missed that, sorry. Yes please push it to jdk9, it will do the job
there too...
Thanks
Miran
On 24/01/14 11:12, Chris Hegarty wrote:
Miran,
This bug has not been approved for JDK 8, in fact it was considered
and rejected. The fix should be pushed to jdk9/dev, if applicable. If
Hi Miran, did you get any response on this yet?
MartiNG
On 17/01/14 10:57, Miroslav Kos wrote:
Hi Steve and Alan,
I just reminding this issue - I have no response from anybody yet and
it would really simplify our integration if I could handle copyright
years inconsistencies this way - I see
On 23 Jan 2014, at 08:53, Martin Grebac martin.gre...@oracle.com wrote:
Hi Miran, did you get any response on this yet?
MartiNG
On 17/01/14 10:57, Miroslav Kos wrote:
Hi Steve and Alan,
I just reminding this issue - I have no response from anybody yet and it
would really simplify our
Hi Steve and Alan,
I just reminding this issue - I have no response from anybody yet and it
would really simplify our integration if I could handle copyright years
inconsistencies this way - I see this issue in many jdk branches and
these each-branch-different changes make each integration
Hi,
this is about fixing copyright years for jdk8 (!); the incorrect years
found for both 2012 and 2013, so not to confuse script
jdk8/make/scripts/update_copyright_year.sh
it is necessary to use option -d date for commit. I tested that and
it seems to work perfect.
I used following:
[2012
