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
doc: new process docs and various updates #158
Conversation
A number of updates mainly focused on paving the way for multiple maintainers and making better use of the GitHub vulnerability reporting tools. Signed-off-by: Paul Moore <paul@paul-moore.com>
These are the changes from issue #146, still look okay to you @drakenclimber? If so, can I get an ACK? |
Ping @drakenclimber ? |
The maintainer which merged the patch into the repository should add their | ||
sign-off after ensuring that it is correct to do so (see the documentation on | ||
submitting patches); if it is not correct for the maintainer to add their | ||
sign-off, it is likely they patch should not be merged. The maintainer should |
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.
it is likely they patch
nitpick - it is likely the patch
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.
Nice catch, fixed.
Sorry about that. I was out a few days, and obviously spacing off a few others :(. I had one really nitpicky comment, but otherwise it looks really good. Thanks for putting it together.
|
Thanks @drakenclimber, I fixed the typo you found, added your ACK, and merged the patch as 4bec773. |
A number of updates mainly focused on paving the way for multiple
maintainers and making better use of the GitHub vulnerability
reporting tools.
Signed-off-by: Paul Moore paul@paul-moore.com