Bump version for release.
This commit is contained in:
parent
127ad1dd1f
commit
00d1dea94e
3 changed files with 5 additions and 5 deletions
2
NEWS
2
NEWS
|
@ -1,4 +1,4 @@
|
|||
1.7.11.dev0
|
||||
1.7.11
|
||||
* #479, #588: BREAKING: Automatically use the "archive_name_format" option to filter which archives
|
||||
get used for borgmatic actions that operate on multiple archives. Override this behavior with the
|
||||
new "match_archives" option in the storage section. This change is "breaking" in that it silently
|
||||
|
|
|
@ -162,9 +162,9 @@ You can the `--log-file-verbosity` flag to customize the log file's log level:
|
|||
borgmatic --log-file /path/to/file.log --log-file-verbosity 2
|
||||
```
|
||||
|
||||
<span class="minilink minilink-addedin">New in borgmatic version 1.7.11</span>
|
||||
Use the `--log-file-format` flag to override the default log message format.
|
||||
This format string can contain a series of named placeholders wrapped in curly
|
||||
<span class="minilink minilink-addedin">New in version 1.7.11</span> Use the
|
||||
`--log-file-format` flag to override the default log message format. This
|
||||
format string can contain a series of named placeholders wrapped in curly
|
||||
brackets. For instance, the default log format is: `[{asctime}] {levelname}:
|
||||
{message}`. This means each log message is recorded as the log time (in square
|
||||
brackets), a logging level name, a colon, and the actual log message.
|
||||
|
|
2
setup.py
2
setup.py
|
@ -1,6 +1,6 @@
|
|||
from setuptools import find_packages, setup
|
||||
|
||||
VERSION = '1.7.11.dev0'
|
||||
VERSION = '1.7.11'
|
||||
|
||||
|
||||
setup(
|
||||
|
|
Loading…
Reference in a new issue