- Rebase before opening a pull request
- If you are sending several unrelated fixes or features, use a branch and a separate pull request for each
- If possible try squashing everything in a single commit. This is particularly beneficial in the case of feature merges since it allows easy bisecting when a problem arises
- RetroArch codebase follows C89 coding rules for portability across many old platforms check using
C89_BUILD=1
[Description of the pull request, detail any issues you are fixing or any features you are implementing]
[Any issues this pull request may be addressing]
[Any other PRs from related repositories that might be needed for this pull request to work]
[If possible @mention all the people that should review your pull request]