summaryrefslogtreecommitdiff
path: root/libpod/boltdb_state_unsupported.go
diff options
context:
space:
mode:
authorSascha Grunert <sgrunert@suse.com>2020-08-25 21:48:18 +0200
committerSascha Grunert <sgrunert@suse.com>2020-08-28 12:09:08 +0200
commitd02cb2ddc014b6ebf14aea06254fb8d85a548e07 (patch)
tree517a999672cbf54e06fa103d65fa1ac21fc77494 /libpod/boltdb_state_unsupported.go
parent061c93f70101026d79cca6e75ac0c565e1fa99ec (diff)
downloadpodman-d02cb2ddc014b6ebf14aea06254fb8d85a548e07.tar.gz
podman-d02cb2ddc014b6ebf14aea06254fb8d85a548e07.tar.bz2
podman-d02cb2ddc014b6ebf14aea06254fb8d85a548e07.zip
Fix log level case regression
With previous versions of Podman (like v1.9.2) it was always possible to specify the log level in any case, for example `INFO`. This behavior has silently changed, where the `--log-level` flag only accepts lower case levels. This commit re-enables the old behavior and adds an e2e test for it. Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Diffstat (limited to 'libpod/boltdb_state_unsupported.go')
0 files changed, 0 insertions, 0 deletions