-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split the sources #24
Comments
Why not? This could be done while someone is working on a core. |
I'm happy with the current structure BUT! I'm happy to prune dead cores. If there are cores that arent getting love let me know and I'll pick them up. |
Hi Stephen, If you mean improving some older cores, may I suggest the NES and Gameboy They could use a bit of work to improve compatibility (specifically, Thanks,
|
As I'm usually hacking on several cores at a time, my local repo has a lot of "garbage" (unfinished or experimental code). I think it would be easier to handle with separate repos for the cores. If it's OK, I can generate FPGA64, C16, BBC-micro, Archimedes repos with this method: |
Yes, of course feel free to cut things. When I started I didn't expect much more than the Atari st and the Minimig. But that prediction was slightly wrong .... |
MiST is like a good wine, it just gets better with age :) |
It's done. |
@harbaum,
Could you consider to split the sources of cores into separate repositories?
It will be more easier to provide the support because developers can work on specific cores without forking into separate repo.
Also, it would give a chance to prune non-used sources. For example ZX and minimig cores are no longer used in this repository and may mislead new developers.
Wiki already provides links for repositories for each core, so it can be used as a central hub to gather all used repositories.
The text was updated successfully, but these errors were encountered: