mountcomposefs: Handle empty basedir option #265
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
Fail with an error message if any of the basedir option paths is an empty string. Signed-off-by: Erik Sjölund <[email protected]>
eriksjolund
force-pushed
the
handle-empty-basedir-option
branch
from
c8dc5d3 to
a96f786
Compare
cgwalters
reviewed
Mar 25, 2024
|
An empty string might occur anywhere in the colon-separated list. |
This comment was marked as outdated.
This comment was marked as outdated.
cgwalters
approved these changes
Mar 25, 2024
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.
Fail with an error message if any of the
basedir option paths is an empty string.