8255264: Support for identifying the full range of IPv4 localhost addresses on Windows

[macarte]

Backport of JDK-8255264

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8255264: Support for identifying the full range of IPv4 localhost addresses on Windows

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/627/head:pull/627
$ git checkout pull/627

Update a local copy of the PR:
$ git checkout pull/627
$ git pull https://git.openjdk.java.net/jdk11u-dev pull/627/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 627

View PR using the GUI difftool:
$ git pr show -t 627

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/627.diff

[bridgekeeper]

👋 Welcome back macarte! A progress list of the required criteria for merging this PR into pr/626 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 03: Full - Incremental (ba6adc37)
• 02: Full - Incremental (7da5323f)
• 01: Full - Incremental (c1559676)
• 00: Full (44687456)

[RealCLanger]

Same here... after you've rebased #626 correctly, rebase this PR's source branch to the source branch of #626. Then we should only see one commit in this PR and everything will look good.

[macarte]

/integrate

[openjdk]

@macarte This pull request has not yet been marked as ready for integration.

[macarte]

right, have to wait for #626 to be commited first

[openjdk-notifier]

The dependent pull request has now been integrated, and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout 8250521
git fetch https://git.openjdk.java.net/jdk11u-dev master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[RealCLanger]

Can you rebase this PR onto current master? Then it should become clean again...

[macarte]

/integrate

[openjdk]

@macarte This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8255264: Support for identifying the full range of IPv4 localhost addresses on Windows

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

⚠️ @macarte This pull request contains merges that bring in commits not present in the target repository. Since this is not a "merge style" pull request, these changes will be squashed when this pull request in integrated. If this is your intention, then please ignore this message. If you want to preserve the commit structure, you must change the title of this pull request to Merge <project>:<branch> where <project> is the name of another project in the OpenJDK organization (for example Merge jdk:master).

[openjdk]

@macarte
Your change (at version ba6adc3) is now ready to be sponsored by a Committer.

[RealCLanger]

/sponsor

[openjdk]

Going to push as commit 5d99c71.

[openjdk]

@RealCLanger @macarte Pushed as commit 5d99c71.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.