error: always write errors to stderr #103
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
giuseppe
changed the title
giuseppe
force-pushed
the
write-always-errors-to-stderr
branch
from
c69fd8f
to
1dbafb4
Compare
giuseppe
changed the title
giuseppe
changed the title
|
LGTM |
make sure errors are always written to stderr, even in case a different --log=FILE is specified. Closes: containers#102 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
giuseppe
force-pushed
the
write-always-errors-to-stderr
branch
from
1dbafb4
to
5a89c3c
Compare
giuseppe
changed the title
|
LGTM |
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.
make sure errors are always written to stderr, even in case a
different --log=FILE is specified.
Closes: #102
Signed-off-by: Giuseppe Scrivano gscrivan@redhat.com