Skip to content
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

JDK-8261003 : Bad Copyright header format after JDK-8183372 #2365

Closed
wants to merge 1 commit into from

Conversation

@mahendrachhipa
Copy link
Contributor

@mahendrachhipa mahendrachhipa commented Feb 2, 2021


Progress

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

Issue

  • JDK-8261003: Bad Copyright header format after JDK-8183372

Reviewers

Download

$ git fetch https://git.openjdk.java.net/jdk pull/2365/head:pull/2365
$ git checkout pull/2365

@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented Feb 2, 2021

👋 Welcome back mahendrachhipa! 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 openjdk bot commented Feb 2, 2021

@mahendrachhipa The following label will be automatically applied to this pull request:

  • core-libs

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.

@openjdk openjdk bot added the core-libs label Feb 2, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Feb 2, 2021

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

8261003: Bad Copyright header format after JDK-8183372

Reviewed-by: bchristi

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. Possible candidates are the reviewers of this PR (@bchristi-git) but any other Committer may sponsor as well.

➡️ 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).

@mahendrachhipa
Copy link
Contributor Author

@mahendrachhipa mahendrachhipa commented Feb 2, 2021

/integrate

@openjdk openjdk bot added the sponsor label Feb 2, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Feb 2, 2021

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

@bchristi-git
Copy link
Member

@bchristi-git bchristi-git commented Feb 2, 2021

/sponsor

@openjdk openjdk bot closed this Feb 2, 2021
@openjdk
Copy link

@openjdk openjdk bot commented Feb 2, 2021

@bchristi-git @mahendrachhipa Pushed as commit 9af3339.

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

@mlbridge
Copy link

@mlbridge mlbridge bot commented Feb 2, 2021

Webrevs

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