Skip to content

Conversation

MBaesken
Copy link
Member

@MBaesken MBaesken commented Oct 17, 2025

Clean backport


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8362516 needs maintainer approval

Issue

  • JDK-8362516: Support of GCC static analyzer (-fanalyzer) (Enhancement - P4 - Approved)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/2354/head:pull/2354
$ git checkout pull/2354

Update a local copy of the PR:
$ git checkout pull/2354
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/2354/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2354

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/2354.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 17, 2025

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

@openjdk
Copy link

openjdk bot commented Oct 17, 2025

@MBaesken 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:

8362516: Support of GCC static analyzer (-fanalyzer)

Reviewed-by: lucy

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 15 new commits pushed to the master branch:

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 master branch, type /integrate in a new comment.

@openjdk openjdk bot changed the title Backport ba90ccc6a8ca7b0b728568ea614470c85a5f7f8a 8362516: Support of GCC static analyzer (-fanalyzer) Oct 17, 2025
@openjdk
Copy link

openjdk bot commented Oct 17, 2025

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

@openjdk openjdk bot added backport Port of a pull request already in a different code base approval Requires approval; will be removed when approval is received rfr Pull request is ready for review and removed approval Requires approval; will be removed when approval is received labels Oct 17, 2025
@mlbridge
Copy link

mlbridge bot commented Oct 20, 2025

Webrevs

Copy link
Contributor

@RealLucy RealLucy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Oct 20, 2025
@MBaesken
Copy link
Member Author

Thanks for the review !

/integrate

@openjdk
Copy link

openjdk bot commented Oct 20, 2025

Going to push as commit 199a2d9.
Since your change was applied there have been 15 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Oct 20, 2025
@openjdk openjdk bot closed this Oct 20, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Oct 20, 2025
@openjdk
Copy link

openjdk bot commented Oct 20, 2025

@MBaesken Pushed as commit 199a2d9.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport Port of a pull request already in a different code base integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

2 participants