<feed xmlns='http://www.w3.org/2005/Atom'>
<title>eglantine-cirakg/src/yuzu/compatdb.cpp, branch nx2</title>
<subtitle>Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine.</subtitle>
<id>https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2</id>
<link rel='self' href='https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2'/>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/'/>
<updated>2026-07-12T07:32:11+00:00</updated>
<entry>
<title>[qt] nuke game compat list (again) (#4201)</title>
<updated>2026-07-12T07:32:11+00:00</updated>
<author>
<name>lizzie</name>
<email>lizzie@eden-emu.dev</email>
</author>
<published>2026-07-12T07:32:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=7f85c6e2823d34bfa32cae6d52a44846f8553731'/>
<id>urn:sha1:7f85c6e2823d34bfa32cae6d52a44846f8553731</id>
<content type='text'>
we have no use for it
it's dead code
most of the time users just complain about how the list isn't updated
ok so what if we update it? great now its more noise added to the git, awesome
even if we constantly update it, we introduce new breakage that makes keeping
track of things extremely difficult

either we integrate with emuready (would violate self containment principles)

or we integrate with emuready in a similar fashion to eden news outlet
(where we cache the list with some TTL of like 60 mins or whatever)
that would be better respecting of "self containment" but would probably
require having a quick way to update the list additively, probably filtered to the user's
device instead of a global thing, and i dont think emuready has that granularity
nor we have the "connect this to that" for the api stuffs

another (which is what i propose here) is throw everything out of the window
until someone can come up with something better

Signed-off-by: lizzie &lt;lizzie@eden-emu.dev&gt;

Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/4201
Reviewed-by: Maufeat &lt;sahyno1996@gmail.com&gt;
Reviewed-by: CamilleLaVey &lt;camillelavey99@gmail.com&gt;
</content>
</entry>
<entry>
<title>[common/logging] Simplify logging logic and fix issues when logging before system is created (#3688)</title>
<updated>2026-03-12T17:29:15+00:00</updated>
<author>
<name>lizzie</name>
<email>lizzie@eden-emu.dev</email>
</author>
<published>2026-03-12T17:29:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=395613b01f918b559f0a3b1718c78f81987c49d4'/>
<id>urn:sha1:395613b01f918b559f0a3b1718c78f81987c49d4</id>
<content type='text'>
- our logging code was bigger than spdlog itself, why???? just keep it simple
- fix issues when logging before logging system is even started
- removes the "initialized logging twice" issue
- removes uneeded indirection in file logging
- uses direct formatting instead of jumping hoopla-around the fmt::format() ressult
- code duplication and dead code removal as usual

I did explore dup2() but I think it's not worth the hassle
I did try `fwopen()` but it's better if things are just kept as-is.

there is a lot of noise because I removed a bunch of redundant files on logging and just put everything in one file

now normally this wouldn't be a good idea, however consider: the complexity of logging; it's less than 500 lines... does it really need a whole subsystem?!?!?! ITS JUST LOGGING

Signed-off-by: lizzie &lt;lizzie@eden-emu.dev&gt;
Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/3688
Reviewed-by: crueter &lt;crueter@eden-emu.dev&gt;
Reviewed-by: DraVee &lt;chimera@dravee.dev&gt;
Reviewed-by: CamilleLaVey &lt;camillelavey99@gmail.com&gt;
Co-authored-by: lizzie &lt;lizzie@eden-emu.dev&gt;
Co-committed-by: lizzie &lt;lizzie@eden-emu.dev&gt;
</content>
</entry>
<entry>
<title>[desktop] Data Manager, data import/export (#2700)</title>
<updated>2025-10-15T02:54:41+00:00</updated>
<author>
<name>crueter</name>
<email>crueter@eden-emu.dev</email>
</author>
<published>2025-10-15T02:54:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=5f9dba40a0fe71ccd7014ae37a2fbfd8f225396e'/>
<id>urn:sha1:5f9dba40a0fe71ccd7014ae37a2fbfd8f225396e</id>
<content type='text'>
This adds a "Data Manager" dialog to the Tools menu. The Data Manager allows for the following operations:
- Open w/ system file manager
- Clear
- Export
- Import

On any of the following directories:
- Save (w/ profile selector)
- UserNAND
- SysNAND
- Mods
- Shaders

TODO for the future:
- "Cleanup" for each directory
- TitleID -&gt; Game name--let users clean data for a specific game if applicable

Signed-off-by: crueter &lt;crueter@eden-emu.dev&gt;
Reviewed-on: https://git.eden-emu.dev/eden-emu/eden/pulls/2700
Reviewed-by: MaranBr &lt;maranbr@eden-emu.dev&gt;
Reviewed-by: Lizzie &lt;lizzie@eden-emu.dev&gt;
</content>
</entry>
<entry>
<title>Removed telemetry and anonymized SCM (git) strings</title>
<updated>2025-04-04T01:40:47+00:00</updated>
<author>
<name>darktux</name>
<email>darktux@y2nlvhmmk5jnsvechppxnbyzmmv3vbl7dvzn6ltwcdbpgxixp3clkgqd.onion</email>
</author>
<published>2024-04-04T23:58:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=2032d035a344cc6a6868ab3c6f0e7250b1f745ea'/>
<id>urn:sha1:2032d035a344cc6a6868ab3c6f0e7250b1f745ea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>general: fix spelling mistakes</title>
<updated>2023-03-12T15:33:01+00:00</updated>
<author>
<name>Liam</name>
<email>byteslice@airmail.cc</email>
</author>
<published>2023-03-12T03:10:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=5be8a74b0cc4a256106b88a3765f9c2c49ade2f8'/>
<id>urn:sha1:5be8a74b0cc4a256106b88a3765f9c2c49ade2f8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge pull request #9229 from Docteh/achy_breaky_heart</title>
<updated>2022-11-18T00:20:18+00:00</updated>
<author>
<name>Morph</name>
<email>39850852+Morph1984@users.noreply.github.com</email>
</author>
<published>2022-11-18T00:20:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=ab4c53a3e61ef8ab311f638d7b74c87543df5d34'/>
<id>urn:sha1:ab4c53a3e61ef8ab311f638d7b74c87543df5d34</id>
<content type='text'>
Add break for default cases</content>
</entry>
<entry>
<title>Add break for default cases</title>
<updated>2022-11-14T00:30:55+00:00</updated>
<author>
<name>Kyle Kienapfel</name>
<email>Docteh@users.noreply.github.com</email>
</author>
<published>2022-11-11T12:12:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=d886438754811b3529e2336464080e760d0794f8'/>
<id>urn:sha1:d886438754811b3529e2336464080e760d0794f8</id>
<content type='text'>
Visual Studio has an option to search all files in a solution, so I
did a search in there for "default:" looking for any missing break
statements.

I've left out default statements that return something, and that throw
something, even if via ThrowInvalidType. UNREACHABLE leads towards throw

R_THROW macro leads towards a return
</content>
</entry>
<entry>
<title>yuzu/compatdb: Rework compatibility submission system</title>
<updated>2022-11-10T20:36:22+00:00</updated>
<author>
<name>FearlessTobi</name>
<email>thm.frey@gmail.com</email>
</author>
<published>2022-10-26T13:03:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=8c677c24a5a3ae63ef9d95c751cb47b289bfa6a4'/>
<id>urn:sha1:8c677c24a5a3ae63ef9d95c751cb47b289bfa6a4</id>
<content type='text'>
Co-Authored-By: Narr the Reg &lt;5944268+german77@users.noreply.github.com&gt;
</content>
</entry>
<entry>
<title>chore: make yuzu REUSE compliant</title>
<updated>2022-07-27T10:53:49+00:00</updated>
<author>
<name>Andrea Pappacoda</name>
<email>andrea@pappacoda.it</email>
</author>
<published>2022-05-15T00:06:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=6a2efdda2f7075331cab36901a30d511468f60e7'/>
<id>urn:sha1:6a2efdda2f7075331cab36901a30d511468f60e7</id>
<content type='text'>
[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
</content>
</entry>
<entry>
<title>yuzu qt: Remove global system instances from config, WaitTree, main</title>
<updated>2021-10-07T17:50:13+00:00</updated>
<author>
<name>lat9nq</name>
<email>22451773+lat9nq@users.noreply.github.com</email>
</author>
<published>2021-09-03T01:40:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.cirakg.xyz/eglantine-cirakg/commit/?id=3aec34df0afe4c96bc3b340c2af02460f769329a'/>
<id>urn:sha1:3aec34df0afe4c96bc3b340c2af02460f769329a</id>
<content type='text'>
</content>
</entry>
</feed>
