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

Please add info on what's new #18

Open
mardy opened this issue Jan 5, 2023 · 2 comments
Open

Please add info on what's new #18

mardy opened this issue Jan 5, 2023 · 2 comments

Comments

@mardy
Copy link
Contributor

mardy commented Jan 5, 2023

Hi!
I just found this project by accident, and I miss some paragraph in the README file that would explain what's the difference between this project and the original libogc. It seems that libogc is still maintained, so I'm hoping that the improvement made in libogc2 will eventually land in libogc too.

@eku
Copy link

eku commented May 10, 2023

Also, GitHub does not identify this as a fork of the original libogc. So how did this one come about?

@Extrems
Copy link
Member

Extrems commented May 10, 2023

There's a pretty simple explanation for that: A user/organization can only have one fork associated with it, and this organization already had one (extremscorner/libogc-rice). So duplicating was the only option.

This came about as an attempt to reconcile libogc and libogc-rice, but some incidents occurred and there's now no chance of the changes making their way back upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants