forked from scummvm/scummvm
-
Notifications
You must be signed in to change notification settings - Fork 31
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #150 from RobLoach/update-2.1.0
LIBRETRO: Update to ScummVM 2.1.0
- Loading branch information
Showing
4,570 changed files
with
833,833 additions
and
237,579 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
/po/cs_CZ.po encoding=iso-8859-2 | ||
/po/hu_HU.po encoding=iso-8859-2 | ||
/po/pl_PL.po encoding=iso-8859-2 | ||
/po/be_BY.po encoding=iso-8859-5 | ||
/po/ru_RU.po encoding=iso-8859-5 | ||
/po/uk_UA.po encoding=iso-8859-5 | ||
/po/el.po encoding=iso-8859-7 | ||
/po/he.po encoding=iso-8859-8 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
|
||
Thank you for contributing to ScummVM. Please read the following carefully before submitting your Pull Request. | ||
|
||
Make sure your individual commits follow the guidelines found in the ScummVM Wiki: https://wiki.scummvm.org/index.php?title=Commit_Guidelines. If they're not please edit them before submitting the Pull Request. | ||
|
||
Commits and Pull Requests should use the following template: | ||
|
||
``` | ||
SUBSYSTEM: Short (50 chars or less) summary of changes | ||
More detailed explanatory text, if necessary. Wrap it to about 72 | ||
characters or so. In some contexts, the first line is treated as the | ||
subject of an email and the rest of the text as the body. The blank | ||
line separating the summary from the body is critical (unless you omit | ||
the body entirely); tools like rebase can get confused if you run the | ||
two together. | ||
Write your commit message in the present tense: "Fix bug" and not "Fixed | ||
bug." This convention matches up with commit messages generated by | ||
commands like git merge and git revert. | ||
Further paragraphs come after blank lines. | ||
- Bullet points are okay, too | ||
- Typically a hyphen or asterisk is used for the bullet, preceded by a | ||
single space, with blank lines in between, but conventions vary here | ||
- Use a hanging indent | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.