Added more information about upgrade-conf source flag #5256
Conversation
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
This removes a little information from the general 'efm' utility page and adds a note to see the upgrade page for more info instead. Hopefully this is better than having incomplete information spread out across pages. On the upgrade page there is now a whole section on the -source parameter and when root privileges are not required to run it. There is also a note about what happens when files already exist in the target location. The above changes are in response to a customer confused about when root privileges were required or not, and what happened when files are upgraded into the same directory as the source files (source files renamed). Any suggestions are welcome -- the "summary" could possibly be a table but that might be overkill.
EFM-Bobby
added
the
deploy
EFM-Bobby
commented
Feb 12, 2024
github-actions
bot
temporarily deployed
to
pr-5256-efm-upgrade-source-flag-details
github-actions
bot
temporarily deployed
to
pr-5256-efm-upgrade-source-flag-details
This removes a little information from the general 'efm' utility page and adds a note to see the upgrade page for more info instead. Hopefully this is better than having incomplete information spread out across pages. On the upgrade page there is now a whole section on the -source parameter and when root privileges are not required to run it. There is also a note about what happens when files already exist in the target location. The above changes are in response to a customer confused about when root privileges were required or not, and what happened when files are upgraded into the same directory as the source files (source files renamed). Any suggestions are welcome -- the "summary" could possibly be a table but that might be overkill.
djw-m
force-pushed
the
efm/upgrade-source-flag-details
branch
from
710962b to
737d19b
Compare
github-actions
bot
temporarily deployed
to
pr-5256-efm-upgrade-source-flag-details
… into efm/upgrade-source-flag-details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This removes a little information from the general 'efm' utility page and adds a note to see the upgrade page for more info instead. Hopefully this is better than having incomplete information spread out across pages. On the upgrade page there is now a whole section on the -source parameter and when root privileges are not required to run it.
There is also a note about what happens when files already exist in the target location.
The above changes are in response to a customer confused about when root privileges were required or not, and what happened when files are upgraded into the same directory as the source files (source files renamed). Any suggestions are welcome -- the "summary" could possibly be a table but that might be overkill.