Can't you discuss that in a PM?
Better yet, read the freaking license. It's public and there are tons of pages devoted to make sure everyone understands the license.
You can even watch a video which explains it..
I won't confirm or tell you what to do anymore. It's just too much work and you'll violate it again anyway because you don't understand the concept of Open Source. (As you ask a specific question, I answer it; then you do something else than you originally asked or intended to do)
As a final attempt, here are some parts of the license broken down for you to get you started:
There are 3 (!) important clauses. Combined, probably shorter than the entire GPL discussion we've had over the past week. So please, just read this:
Mostly ethical mumbo-jumbo and describes where this license applies:
https://github.com/citra-emu/citra/blob/master/license.txt#L1
Clause 1:
https://github.com/citra-emu/citra/blob/master/license.txt#L79
Clause 2:
https://github.com/citra-emu/citra/blob/master/license.txt#L90
Clause 3:
https://github.com/citra-emu/citra/blob/master/license.txt#L134
Starting here is mostly legal mumbo-jumbo:
https://github.com/citra-emu/citra/blob/master/license.txt#L171
(It's probably enough to read 1,2 and 3, but ideally you should have read all of it as you agree'd to this license..)
You can skip the next part of my post, I'd recommend to read the license instead as it's more detailed.
Just read it if you read the license and still don't get it (as the license was written in pre-internet days).
If you don't get it after reading this part either: You can't agree to our license then (which means you are unable to share any derivative works or the work itself)
Specifically you broke this rule in the past (part of clause 2):
https://github.com/citra-emu/citra/blob/master/license.txt#L95 .
It's a very concrete requirement. Consider git metadata to be part of the file (Meaning: If you move changes around without git you'll likely cause a GPL violation as the metadata will be lost). This also means: If you don't know how to use git, you'll likely always cause a GPL violation unless you download a version of the code, compile it as-is, do your funky hex-edits, then document exactly where/how you downloaded the source, at what version, on what date and then describe all your hex-changes in a changelog as clean as possible + reasoning for these changes.
You've also violated this one (part of clause 3):
https://github.com/citra-emu/citra/blob/master/license.txt#L142 (it's not enough to provide ANY version but you must provide the exact version that you have used. People should be able to download the source code, compile it, make your hex modifications and have the exactly same version as you do). If you add a ton of links it's impossible to do this. If you don't add correct links and expect people to find source code on their own, it's also a violation.
If you ship binary and source code independently you must include the license.txt and README.md with both. Also your binary package must be accompanied by a written offer for the source code (check clause 3). If it doesn't it's a GPL violation. Linking to the source code from the post is not enough. As soon as someone downloads your binary the wouldn't know the code is licensed under the GPL. If they reupload it other people wouldn't know either and so on.
So anything licensed under the GPL must include those 2 files. Binary releases must include (!) exact information where to get the source code which was used to create that particular binary (valid for 3 more years from the day the binary is not available anymore).
(You broke theses rules in various ways before, but I can't be bothered to list all of them or the specifics)
---
This is hopefully the last post about licensing here. Anything further should be discussed via private conversations.
However, I'm also done explaining the GPL, I won't do it again unless you have questions which are not answered by me in the past, the license or if there are conflicts in my posts and the license (Hint: the license is legally binding, my post is not).
