muskit/spice2x.github.io
0
0
Fork 0
mirror of https://github.com/spice2x/spice2x.github.io.git synced 2026-08-01 14:20:42 -07:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
sp2xdev
2024-04-25 17:27:51 -07:00
committed by GitHub
parent df5da69be6
commit ab2625ec73
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -1
View File
@@ -49,7 +49,7 @@ Baseline rules for patch submissions are as follows. Any patches violating the r
* Test for regressions, at least in and around the component you are modifying: * Test for regressions, at least in and around the component you are modifying:
* All currently supported games / versions must continue to work. * All currently supported games / versions must continue to work.
* Backwards compatibility must be preserved, unless there is a really good reason to break it. This includes (but not limited to): global/local config files, command line parameters, gmae patches, device interop (e.g., card readers), and SpiceAPI / Companion interop. * Backwards compatibility must be preserved, unless there is a really good reason to break it. This includes (but not limited to): global/local config files, command line parameters, game patches, device interop (e.g., card readers), and SpiceAPI / Companion interop.
* Simply put, if someone has an existing install of spice2x, copying over new version of spice2x should not result in different behavior or loss of functionality. * Simply put, if someone has an existing install of spice2x, copying over new version of spice2x should not result in different behavior or loss of functionality.
* Make sure you compile with the included Docker script and ensure you do not introduce any new compiler warnings or build breaks; otherwise, your patch will not be accepted. The Docker script is the standard build environment, your custom Linux build environment or MSVC can be used for development but you must validate the final build using Docker. * Make sure you compile with the included Docker script and ensure you do not introduce any new compiler warnings or build breaks; otherwise, your patch will not be accepted. The Docker script is the standard build environment, your custom Linux build environment or MSVC can be used for development but you must validate the final build using Docker.
* Do not submit snippets of code as a "patch". Exceptions can be made for trivial changes (correct a typo, fix a single line of code...), but otherwise, a successfully compiled & fully tested patch file is required when submitting for review. * Do not submit snippets of code as a "patch". Exceptions can be made for trivial changes (correct a typo, fix a single line of code...), but otherwise, a successfully compiled & fully tested patch file is required when submitting for review.