Hostname(s) documentation #1033
Merged
Conversation
This file contains 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
teclator
reviewed
Feb 5, 2020
Co-Authored-By: Knut Alejandro Anderssen González <kanderssen@suse.de>
teclator
reviewed
Feb 5, 2020
teclator
reviewed
Feb 5, 2020
|
NP: I would split the PR moving the fixes to a different PR |
as customer wishes ;-) |
teclator
reviewed
Feb 18, 2020
teclator
reviewed
Feb 18, 2020
teclator
reviewed
Feb 18, 2020
mvidner
reviewed
Feb 18, 2020
Co-Authored-By: Martin Vidner <martin@vidner.net>
Co-Authored-By: Martin Vidner <martin@vidner.net>
Co-Authored-By: Martin Vidner <martin@vidner.net>
Co-Authored-By: Knut Alejandro Anderssen González <kanderssen@suse.de>
Co-Authored-By: Knut Alejandro Anderssen González <kanderssen@suse.de>
mvidner
approved these changes
Feb 21, 2020
|
✔️ Public Jenkins job #131 successfully finished |
|
✔️ Internal Jenkins job #67 successfully finished |
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.
Problem
The hostname / DNS setup has changed recently in YaST and the user miss some of the options that YaST allowed in the past. Thus, the documentation should be updated reflecting the new changes and clarifying why some of the options do not make sense anymore.