Skip to content
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

Add downstream kernels for cloud providers #398

Open
tleb opened this issue Mar 6, 2025 · 1 comment
Open

Add downstream kernels for cloud providers #398

tleb opened this issue Mar 6, 2025 · 1 comment
Labels
new-project Requests to add support for new projects to Elixir

Comments

@tleb
Copy link
Member

tleb commented Mar 6, 2025

Reading this article:

The easiest way to do this is to use an online kernel source browser like this one. This allows you to easily switch between different kernel versions and lookup symbols appearing in the stacktrace. Although it does not index kernel code used by GCP or AWS it is still very handy.

Highlight is my own.

This is not really our field but it should be rather straight forward:

  1. Find the Git remotes.
  2. Rename the Git tags from those remotes inside script.sh.

Only question: how should the tags be structured? Add entries inside the existing minor menus? Add new minor menus for those kernels? Add new major menus?

Nothing urgent.

@tleb tleb added the new-project Requests to add support for new projects to Elixir label Mar 6, 2025
@fstachura
Copy link
Collaborator

Maybe having a separate entry for linux-gcp, linux-aws and linux-android would make sense?
But then it probably would be cool to actually allow users to view diffs between upstream and vendor versions when that gets finished...

The annoying thing about the versions menu is that it's very big, to the point where its impact is noticeable during site load (dir/source view does not flash on musl like it does on linux). I'm wondering if it wouldn't make sense to move it to js. Then having twice the tags we have right now, but for aws/gcp/azure/android... wouldn't be a problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-project Requests to add support for new projects to Elixir
Projects
None yet
Development

No branches or pull requests

2 participants