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 a tracker for patches that have not yet been upstreamed #12

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tgross35
Copy link

@tgross35 tgross35 commented Nov 17, 2023

src/Patch-registry.md Outdated Show resolved Hide resolved
Note that things change frequently and the information in this table may not
always be the latest.

| Target Area | Status | Author | Git Link | Mailing List Link |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting all the information together!

I wonder whether bullet points/lists are better than tables, at very least, we can group things belonging to the same subsystem together. For example:

Filesystem API

vfs

  • Depends on: folio
    ...

MM

folio

...

pages

...

Filesystem implementions

tarfs

  • Depends on: vfs
    ...

puzzle fs

...

Thoughts?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I like the thought of having dependencies. Maybe it would be good to keep the main abstractions in a table for quick reading, but the drivers and implementations could be in a list format?

I'll play around with it a bit

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, tables are better for a quick look (or a rough picture of everything). However, I think people that use the information would probably do a search with key words, so it doesn't matter. Maybe a table for each large subsystem (like MM, filesystems, networking, drm, security, etc.)? But anyway, I don't have any problem with the current format, we can always improve the format of the information later ;-)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Up to you :) if you think it is ok to merge as-is, I can make a PR doing some updates. Maybe even just an extra column saying the subsystem then a second one saying exactly what it is could work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants