-
-
Notifications
You must be signed in to change notification settings - Fork 164
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
folders for crates should be better organized #51
Comments
Yes, definitely. This has been on my mind for a while, since many things are x86-specific. The flat hierarchy is no longer a benefit. |
kevinaboos
added a commit
to kevinaboos/Theseus
that referenced
this issue
May 14, 2021
No source code or functionality changes.
kevinaboos
added a commit
that referenced
this issue
Jul 16, 2021
This commit only reorganizes source code, there are no functionality changes.
ACPI-related crates have been reorganized. Other subsystems to follow. |
github-actions bot
pushed a commit
that referenced
this issue
Jul 16, 2021
This commit only reorganizes source code, there are no functionality changes. 2bc18d7
github-actions bot
pushed a commit
to apogeeoak/theseus
that referenced
this issue
Jul 23, 2021
…. (theseus-os#383) This commit only reorganizes source code, there are no functionality changes. 2bc18d7
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I understand Theseus has a flat modular architecture but that does not mean we should have a flat organization of the code. Can we create a hierarchy to organize the modules?
The text was updated successfully, but these errors were encountered: