-
Notifications
You must be signed in to change notification settings - Fork 23
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
Clarify documentation on sysext types and origins #348
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please squash your commits into a single one and we should be good, thanks.
ded1bba
to
9c562d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wait, you still have one pending conflict to solve before merging.
There is still an extra commit - instead of merging |
1cdc7c2
to
9c562d2
Compare
Signed-off-by: krishjainx <[email protected]>
9c562d2
to
65fbb97
Compare
Done |
Clarify documentation on sysext types and origins
It's confusing to distinguish between non-official sysexts from the sysext-bakery, built-in sysexts, and official ones. I was often asked about this when giving my talk on systemd system extensions in Berlin. This should clear it up! Thanks :)
EDIT: Closes flatcar/Flatcar#1476