fix json file logging filenames#1211
Merged
AkihiroSuda merged 1 commit intocontainerd:masterfrom Jul 10, 2022
Merged
Conversation
fahedouch
force-pushed
the
fix-json-file-logging-filenames
branch
from
19ff023 to
396963e
Compare
Member
Author
|
I made a patch for go-logrorate v0.1.1 to init supporting |
fahedouch
force-pushed
the
fix-json-file-logging-filenames
branch
from
2a3fd99 to
8716087
Compare
Signed-off-by: fahed dorgaa <[email protected]>
fahedouch
force-pushed
the
fix-json-file-logging-filenames
branch
from
8716087 to
41c63f3
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
2 participants
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.
I released the
v0.1.0of go-logrotatethis will fix #1077
Signed-off-by: fahed dorgaa [email protected]