Open
Conversation
Author
|
I noticed some tests are failing. Since it’s late here, I’ll investigate those tomorrow. Also, I’m not sure if I am targeting the correct branch. Please let me know if you would prefer me to rebase onto 6.1 instead. |
santysisi
force-pushed
the
docs/add-sudo-privileges-to-examples
branch
from
5a058bb to
1ae5568
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
sudoto the build example (make installstep) in the documentation.The docs recommend using
sudoprivileges. This change also keeps the instructions consistent with other sections of theMarkdowndocumentation wheresudois already specified for the installation step.