How to contribute to the SDL mirror?

[logiseye]

Hey gus,

I created an issue on the SDL mirror repo (https://github.com/RetroPie/SDL-mirror) a few days back. Unfortunately the response was the most unfriendly thing that occured to me on GitHub so far: there was a two words answer and the issues feature got disabled. No word on how to get involved, where's the right place to ask etc. The door was slammed in my face...

So, how do I contribute to the SDL mirror? Or is that actually a thing you don't want?

[Zigurana]

If I understand correctly, official SDL is not hosted on Github, but on mercurial (here ). To enable easy integration, there are multiple copies of it on guthub (all unofficial).
So the mirror is just that, a copy of the SDL sources that we use for RetroPie.

If there are problems, or if you have other contributions, it's best to file an issue at the mercurial repo, and let the SDL folks look at it. We want our copy to be just a simple copy, and not something we need to merge and maintain.

[BuZz]

@logiseye You misinterpreted my reply. It wasn't meant as rude. I apologise if it come across as that.

I did reply with two words - "no plans", and then seconds later i added "We didn't write the mali driver also.". I then went to the github settings as I thought I had closed it the other day but hadn't. (I thought I had not actually closed it, as I did mean to give you a chance to respond - my bad).

I only opened the issue tracker temporarily recently to mention something to another dev - we never had it enabled before as it would mean we may end up with lots of SDL issues we are not responsible for.

I have re-enabled it, but I really don't think it serves a purpose to have an issue tracker open for our fork (which just contains a few patches on top of sdl which are specific for retropie). The mirror we fork off doesn't have an issue tracker on it either.

BTW - We may also get rid of the Mali code and instead use kmsdrm backend.