Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine. https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2 2022-10-06T19:00:52+00:00 2022-10-06T19:00:52+00:00 Fernando Sahmkow fsahmkow27@gmail.com 2021-12-17T15:45:06+00:00 urn:sha1:0925f2386a2a3750fdd139d36d48a0ade900b5a5 2022-07-27T10:53:49+00:00 Andrea Pappacoda andrea@pappacoda.it 2022-05-15T00:06:02+00:00 urn:sha1:6a2efdda2f7075331cab36901a30d511468f60e7 [REUSE] is a specification that aims at making file copyright information consistent, so that it can be both human and machine readable. It basically requires that all files have a header containing copyright and licensing information. When this isn't possible, like when dealing with binary assets, generated files or embedded third-party dependencies, it is permitted to insert copyright information in the `.reuse/dep5` file. Oh, and it also requires that all the licenses used in the project are present in the `LICENSES` folder, that's why the diff is so huge. This can be done automatically with `reuse download --all`. The `reuse` tool also contains a handy subcommand that analyzes the project and tells whether or not the project is (still) compliant, `reuse lint`. Following REUSE has a few advantages over the current approach: - Copyright information is easy to access for users / downstream - Files like `dist/license.md` do not need to exist anymore, as `.reuse/dep5` is used instead - `reuse lint` makes it easy to ensure that copyright information of files like binary assets / images is always accurate and up to date To add copyright information of files that didn't have it I looked up who committed what and when, for each file. As yuzu contributors do not have to sign a CLA or similar I couldn't assume that copyright ownership was of the "yuzu Emulator Project", so I used the name and/or email of the commit author instead. [REUSE]: https://reuse.software Follow-up to b2eb10382941bef0914f4a0a4685b9033440aa9f 2020-08-15T21:17:52+00:00 Lioncash mathew1800@gmail.com 2020-08-14T13:38:45+00:00 urn:sha1:2ef7815422f4584b334ff196efd72e40ad03e094 Now that clang-format makes [[nodiscard]] attributes format sensibly, we can apply them to several functions within the common library to allow the compiler to complain about any misuses of the functions. 2019-11-13T19:58:43+00:00 Lioncash mathew1800@gmail.com 2019-11-13T19:58:40+00:00 urn:sha1:7d2b1204d7de47291757523eb213ab6f7cc3f749 This is unused, so it can be removed. There's better ways of ensuring zeroed out padding bits, like using zero-initialization, anyhow. 2019-10-26T19:38:30+00:00 Fernando Sahmkow fsahmkow27@gmail.com 2019-10-17T14:35:16+00:00 urn:sha1:ab86995cb9fdb80d39c927899bc70cbb2b6a3f06 2019-10-25T13:01:29+00:00 Fernando Sahmkow fsahmkow27@gmail.com 2019-09-23T18:02:02+00:00 urn:sha1:d4da704ac522baf3c8582e94ec222f0de2363169 2018-09-15T13:21:06+00:00 fearlessTobi thm.frey@gmail.com 2018-09-15T13:21:06+00:00 urn:sha1:1190ea6ddbbcabca5ac0ee73f940f509888f8673 2018-08-07T23:34:47+00:00 Lioncash mathew1800@gmail.com 2018-08-07T17:31:57+00:00 urn:sha1:6b1e9244c06568e6bb981f78a586e4f98a81eacd Uses the C++17 inline variable variants 2018-04-14T03:48:22+00:00 bunnei bunneidev@gmail.com 2018-04-07T04:48:22+00:00 urn:sha1:c30c48e052e461b6d0a855a1a47feed874bc81b2 2017-01-28T14:30:18+00:00 Kloen kloen@outlawkiwi.com 2017-01-28T14:30:18+00:00 urn:sha1:37fa9a488621d890fcb7fd41546951e4ac5c9b13