-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8339845: Update color.org and wapforum.org links to use HTTPS instead of HTTP #21001
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
👋 Welcome back nbenalla! A progress list of the required criteria for merging this PR into |
@nizarbenalla This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 81 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
@nizarbenalla The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The update to HTTPS is appreciated for consistency, though not strictly necessary since HTTP links already redirect to HTTPS. Please ensure all updated links function as expected and align with the project standards.
@@ -690,7 +690,7 @@ private int getRenderingIntent (ICC_Profile profile) { | |||
* shall be set to zero. Thus, we are ignoring two most significant | |||
* bytes here. | |||
* | |||
* See http://www.color.org/ICC1v42_2006-05.pdf, section 7.2.15. | |||
* See https://www.color.org/ICC1v42_2006-05.pdf, section 7.2.15. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@prrace I wanted to clarify if the ICC Specification Doc links need to be updated to the latest one?
https://www.color.org/specification/ICC.1-2022-05.pdf
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be out of scope for this.
@@ -1008,7 +1008,7 @@ public final class BaselineTIFFTagSet extends TIFFTagSet { | |||
/** | |||
* Constant specifying the "ICC Profile" tag. | |||
* | |||
* @see <a href="http://www.color.org/ICC1V42.pdf">ICC Specification, section B.4: Embedding ICC profiles in TIFF files</a> | |||
* @see <a href="https://www.color.org/ICC1V42.pdf">ICC Specification, section B.4: Embedding ICC profiles in TIFF files</a> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here ?
/integrate |
@nizarbenalla |
/sponsor |
@aivanov-jdk This change does not need sponsoring - the author is allowed to integrate it. |
@nizarbenalla Looks you're a committer now. You have to issue the |
I assumed this would be automatically merged once I became a committer. Thank you all for the reviews! /integrate |
Going to push as commit 45e438f.
Your commit was automatically rebased without conflicts. |
@nizarbenalla Pushed as commit 45e438f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
No, the Skara bots don't revisit the PRs after the OpenJDK Census is changed. You weren't a committer when you issued the |
Can I get a review for this doc-only change? I updated some links because the websites moved from HTTP to HTTPS. The redirects can cause some false-positives on tests.
TIA
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/21001/head:pull/21001
$ git checkout pull/21001
Update a local copy of the PR:
$ git checkout pull/21001
$ git pull https://git.openjdk.org/jdk.git pull/21001/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 21001
View PR using the GUI difftool:
$ git pr show -t 21001
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/21001.diff
Webrev
Link to Webrev Comment