10 Commits (6533dfd7cede9ff84b7047e887b2ff86303c964a)

Author	SHA1	Message	Date
Liam	e11a3414ae	ci: fix format task	2 years ago
Liam	30743eff56	ci: make verify format workflow output more helpful	2 years ago
Levi Behunin	d5fc56db4b	Move to Clang Format 15 ... Depends on https://github.com/yuzu-emu/build-environments/pull/69 clang-15 primary run	3 years ago
Colin Kinloch	5d36d4b143	ci: Allow setting clang-format binary	3 years ago
Andrea Pappacoda	cdb240f3d4	chore: make yuzu REUSE compliant ... [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 01cf05bc75	3 years ago
ameerj	31c0f6ca33	ci: Update clang format version	4 years ago
Lioncash	b724a4d90c	General: Tidy up clang-format warnings part 2	5 years ago
Lioncash	1c3490a8db	General: Tidy up clang-format warnings	5 years ago
Lioncash	0105368cc1	ci: Make use of clang-format 10.0 ... 10.0 seems to play nicer with C++ attributes compared to clang-format 6.0.	5 years ago
Zach Hilman	bbc5b5d62d	Finalize Azure Pipelines Definitions ... d	6 years ago