diff --git a/docs/how-to/add-preparation-and-cleanup-steps-to-backups.md b/docs/how-to/add-preparation-and-cleanup-steps-to-backups.md index d6f908559..913f1a9e4 100644 --- a/docs/how-to/add-preparation-and-cleanup-steps-to-backups.md +++ b/docs/how-to/add-preparation-and-cleanup-steps-to-backups.md @@ -28,9 +28,8 @@ hooks: - umount /some/filesystem ``` -New in version 1.6.0 - -The `before_backup` and `after_backup` hooks each run once per repository in a +New in version 1.6.0 The +`before_backup` and `after_backup` hooks each run once per repository in a configuration file. `before_backup` hooks runs right before the `create` action for a particular repository, and `after_backup` hooks run afterwards, but not if an error occurs in a previous hook or in the backups themselves. diff --git a/docs/how-to/deal-with-very-large-backups.md b/docs/how-to/deal-with-very-large-backups.md index 9f219e74c..7c0c20dbc 100644 --- a/docs/how-to/deal-with-very-large-backups.md +++ b/docs/how-to/deal-with-very-large-backups.md @@ -74,10 +74,9 @@ See [Borg's check documentation](https://borgbackup.readthedocs.io/en/stable/usa ### Check frequency -New in version 1.6.2 - -You can optionally configure checks to run on a periodic basis rather than -every time borgmatic runs checks. For instance: +New in version 1.6.2 You can +optionally configure checks to run on a periodic basis rather than every time +borgmatic runs checks. For instance: ```yaml consistency: diff --git a/docs/how-to/inspect-your-backups.md b/docs/how-to/inspect-your-backups.md index 4c9bb4024..318eb6eed 100644 --- a/docs/how-to/inspect-your-backups.md +++ b/docs/how-to/inspect-your-backups.md @@ -53,11 +53,10 @@ borgmatic info ### Searching for a file -New in version 1.6.3 - -Let's say you've accidentally deleted a file and want to find the backup -archive(s) containing it. `borgmatic list` provides a `--find` flag for -exactly this purpose. For instance, if you're looking for a `foo.txt`: +New in version 1.6.3 Let's say +you've accidentally deleted a file and want to find the backup archive(s) +containing it. `borgmatic list` provides a `--find` flag for exactly this +purpose. For instance, if you're looking for a `foo.txt`: ```bash borgmatic list --find foo.txt diff --git a/docs/how-to/make-per-application-backups.md b/docs/how-to/make-per-application-backups.md index f57b9423f..06ff8c65f 100644 --- a/docs/how-to/make-per-application-backups.md +++ b/docs/how-to/make-per-application-backups.md @@ -137,12 +137,11 @@ YAML limitation.) ### Deep merge -New in version 1.6.0 - -borgmatic performs a deep merge of merged include files, meaning that values -are merged at all levels in the two configuration files. Colliding list values -are appended together. This allows you to include common configuration—up to -full borgmatic configuration files—while overriding only the parts you want to +New in version 1.6.0 borgmatic +performs a deep merge of merged include files, meaning that values are merged +at all levels in the two configuration files. Colliding list values are +appended together. This allows you to include common configuration—up to full +borgmatic configuration files—while overriding only the parts you want to customize. diff --git a/docs/how-to/provide-your-passwords.md b/docs/how-to/provide-your-passwords.md index 78cb39036..5afea048b 100644 --- a/docs/how-to/provide-your-passwords.md +++ b/docs/how-to/provide-your-passwords.md @@ -13,12 +13,11 @@ treating those secrets like any other option value. But if you'd rather store them outside of borgmatic, whether for convenience or security reasons, read on. -New in version 1.6.4 - -borgmatic supports interpolating arbitrary environment variables directly into -option values in your configuration file. That means you can instruct -borgmatic to pull your repository passphrase, your database passwords, or any -other option values from environment variables. For instance: +New in version 1.6.4 borgmatic +supports interpolating arbitrary environment variables directly into option +values in your configuration file. That means you can instruct borgmatic to +pull your repository passphrase, your database passwords, or any other option +values from environment variables. For instance: ```yaml storage: