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

Merge foreign-abi #149

Closed
wants to merge 2 commits into from
Closed

Merge foreign-abi #149

wants to merge 2 commits into from

Conversation

@openjdk-bot
Copy link
Contributor

@openjdk-bot openjdk-bot commented May 6, 2020

Hi all,

this is an automatically generated pull request to notify you that there is 1 commit from the branch foreign-abithat can not be merged into the branch foreign-jextract:

The following file contains merge conflicts:

  • test/jdk/java/jextract/smoke.h

All Committers in this project have access to my personal fork and can therefore help resolve these merge conflicts (you may want to coordinate who should do this).
The following paragraphs will give an example on how to solve these merge conflicts and push the resulting merge commit to this pull request.
The below commands should be run in a local clone of your personal fork of the openjdk/panama-foreign repository.

# Ensure target branch is up to date
$ git checkout foreign-jextract
$ git pull https://github.com/openjdk/panama-foreign foreign-jextract

# Fetch and checkout the branch for this pull request
$ git fetch https://github.com/openjdk-bot/panama-foreign +34:openjdk-bot-34
$ git checkout openjdk-bot-34

# Merge the target branch
$ git merge foreign-jextract

When you have resolved the conflicts resulting from the git merge command above, run the following commands to create a merge commit:

$ git add paths/to/files/with/conflicts
$ git commit -m 'Merge foreign-abi'

When you have created the merge commit, run the following command to push the merge commit to this pull request:

$ git push https://github.com/openjdk-bot/panama-foreign openjdk-bot-34:34

Note: if you are using SSH to push commits to GitHub, then change the URL in the above git push command accordingly.

Thanks,
J. Duke


Progress

  • Change must not contain extraneous whitespace
  • Change must be properly reviewed

Download

$ git fetch https://git.openjdk.java.net/panama-foreign pull/149/head:pull/149
$ git checkout pull/149

@openjdk openjdk bot added the failed-auto-merge label May 6, 2020
@bridgekeeper
Copy link

@bridgekeeper bridgekeeper bot commented May 6, 2020

👋 Welcome back duke! A progress list of the required criteria for merging this PR into foreign-jextract will be added to the body of your pull request.

@mlbridge
Copy link

@mlbridge mlbridge bot commented May 6, 2020

@mlbridge
Copy link

@mlbridge mlbridge bot commented May 6, 2020

Mailing list message from Maurizio Cimadamore on panama-dev:

Wasn't expecting this - I'll take a look

Maurizio

On 06/05/2020 15:27, J.Duke wrote:

Hi all,

this is an _automatically_ generated pull request to notify you that there is 1 commit from the branch
`foreign-abi`that can **not** be merged into the branch `foreign-jextract`:

The following file contains merge conflicts:

- test/jdk/java/jextract/smoke.h

All Committers in this [project](https://openjdk.java.net/census#Optional[panama]) have access to my [personal
fork](https://github.com/openjdk-bot/panama-foreign) and can therefore help resolve these merge conflicts (you may want
to coordinate who should do this). The following paragraphs will give an example on how to solve these merge conflicts
and push the resulting merge commit to this pull request. The below commands should be run in a local clone of your
[personal fork](https://wiki.openjdk.java.net/display/skara#Skara-Personalforks) of the
[openjdk/panama-foreign](https://github.com/openjdk/panama-foreign) repository.

# Ensure target branch is up to date
$ git checkout foreign-jextract
$ git pull https://github.com/openjdk/panama-foreign foreign-jextract

# Fetch and checkout the branch for this pull request
$ git fetch https://github.com/openjdk-bot/panama-foreign +34:openjdk-bot-34
$ git checkout openjdk-bot-34

# Merge the target branch
$ git merge foreign-jextract

When you have resolved the conflicts resulting from the `git merge` command above, run the following commands to create
a merge commit:

$ git add paths/to/files/with/conflicts
$ git commit -m 'Merge foreign-abi'

When you have created the merge commit, run the following command to push the merge commit to this pull request:

$ git push https://github.com/openjdk-bot/panama-foreign openjdk-bot-34:34

_Note_: if you are using SSH to push commits to GitHub, then change the URL in the above `git push` command accordingly.

Thanks,
J. Duke

-------------

Commit messages:
- JDK-8244270: reorganize ABI-dependent layout constants (second attempt)

The webrev contains the conflicts with foreign-jextract:
- merge conflicts: https://webrevs.openjdk.java.net/panama-foreign/149/webrev.00.conflicts

Changes: https://git.openjdk.java.net/panama-foreign/pull/149/files
Stats: 1129 lines in 25 files changed: 309 ins; 700 del; 120 mod
Patch: https://git.openjdk.java.net/panama-foreign/pull/149.diff
Fetch: git fetch https://git.openjdk.java.net/panama-foreign pull/149/head:pull/149

PR: https://git.openjdk.java.net/panama-foreign/pull/149

@openjdk
Copy link

@openjdk openjdk bot commented May 6, 2020

@openjdk-bot This change now passes all automated pre-integration checks, type /integrate in a new comment to proceed. After integration, the commit message will be:

Merge foreign-abi
  • If you would like to add a summary, use the /summary command.
  • To credit additional contributors, use the /contributor command.
  • To add additional solved issues, use the /solves command.

There are currently no new commits on the foreign-jextract branch since the last update of the source branch of this PR. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you would like to avoid potential automatic rebasing, specify the current head hash when integrating, like this: /integrate e5a42f2382e85977ed6413e19810c65214665e20.

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 openjdk bot added ready and removed merge-conflict labels May 6, 2020
@openjdk-bot
Copy link
Contributor Author

@openjdk-bot openjdk-bot commented May 6, 2020

/integrate

@openjdk
Copy link

@openjdk openjdk bot commented May 6, 2020

@openjdk-bot
Your change (at version d1ddb81) is now ready to be sponsored by a Committer.

@openjdk openjdk bot added the sponsor label May 6, 2020
@mcimadamore
Copy link
Collaborator

@mcimadamore mcimadamore commented May 6, 2020

/sponsor

@openjdk openjdk bot closed this May 6, 2020
@openjdk openjdk bot added integrated and removed sponsor ready rfr labels May 6, 2020
@openjdk
Copy link

@openjdk openjdk bot commented May 6, 2020

@mcimadamore @openjdk-bot
Pushed as commit 79c0cea.

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

Successfully merging this pull request may close these issues.

None yet

2 participants