From 00d1dea94ea826d8d91d5f6d936c70638889bb32 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Mon, 3 Apr 2023 16:11:25 -0700 Subject: [PATCH] Bump version for release. --- NEWS | 2 +- docs/how-to/inspect-your-backups.md | 6 +++--- setup.py | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/NEWS b/NEWS index dd0a6b6..f693e25 100644 --- a/NEWS +++ b/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 diff --git a/docs/how-to/inspect-your-backups.md b/docs/how-to/inspect-your-backups.md index b6238fe..73020ed 100644 --- a/docs/how-to/inspect-your-backups.md +++ b/docs/how-to/inspect-your-backups.md @@ -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 ``` -New in borgmatic version 1.7.11 -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 +New in version 1.7.11 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. diff --git a/setup.py b/setup.py index bc4e4b7..ad58f0e 100644 --- a/setup.py +++ b/setup.py @@ -1,6 +1,6 @@ from setuptools import find_packages, setup -VERSION = '1.7.11.dev0' +VERSION = '1.7.11' setup(