Ian Wienand b91207ae47 Remove _config_error thrower ... "log and throw" is arguably an anti-pattern; the error message either bubles-up into the exception, or the handler figures it out. We have an example where this logs, and then the handler in blockdevice.py catches it and logs it again. Less layers is better; just raise the exception, and use log.exception to get tracebacks where handled. Change-Id: I8efd94fbe52a3911253753f447afdb7565849185		2017-05-18 10:37:56 +10:00
..
__init__.py	Refactor: block-device filesystem creation, mount and fstab	2017-05-12 13:52:02 +02:00
mkfs.py	Remove _config_error thrower	2017-05-18 10:37:56 +10:00