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.

Sign up for GitHub

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

Jump to bottom

Bump khronos-registry branch to last commit #287

Open
wants to merge 2 commits into
base: khronos-registry
Choose a base branch
from
Open

Bump khronos-registry branch to last commit #287

wants to merge 2 commits into from

Conversation

m-shinder
Copy link

@m-shinder m-shinder commented Jun 3, 2023 •
edited
Loading

Seems like commit 5a281ae was made without moving khronos-registry branch
So fixing it.
Registry versions:

  • OpenGL: 253836ac53b2e248fa47d96cacc18a63ac27c703
  • EGL: a9bef577b041caab108257ea386d0302290d4361

@gurchetansingh
Update OpenGL/EGL registries
5a281ae 
OpenGL: 253836ac53b2e248fa47d96cacc18a63ac27c703
EGL: a9bef577b041caab108257ea386d0302290d4361
@m-shinder
Copy link
Author

Also it seems like khronos-registry branch is useless after Khronos moved to git.
So maybe there is a sense to remove it and remove instructions in registry/README.md

@m-shinder
Update OpenGL/EGL registries
54ce3cf 
OpenGL: 91cdaf381d77b6e700654ecd78cb88a95c1fde1a
Source: https://github.com/KhronosGroup/OpenGL-Registry
EGL: 9ab603608d6b165f79f17eee9ee1ced861625893
Source: https://github.com/KhronosGroup/EGL-Registry
@m-shinder m-shinder mentioned this pull request Jun 3, 2023
Open
@m-shinder
Copy link
Author

Seems github automatically added commit I made for #288
In case of dropping khronos-registry branch, commit 54ce3cf can be picked-out from this PR.

@MrCatNerd
Copy link

any updates on when will this be merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@m-shinder @MrCatNerd @gurchetansingh