Remove some whitespace around "New in version ..." documentation labels.

This commit is contained in:
Dan Helfman 2022-06-16 20:49:15 -07:00
parent cc32f0018b
commit aa013af25e
5 changed files with 19 additions and 24 deletions

View file

@ -28,9 +28,8 @@ hooks:
- umount /some/filesystem
```
<span class="minilink minilink-addedin">New in version 1.6.0</span>
The `before_backup` and `after_backup` hooks each run once per repository in a
<span class="minilink minilink-addedin">New in version 1.6.0</span> 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.

View file

@ -74,10 +74,9 @@ See [Borg's check documentation](https://borgbackup.readthedocs.io/en/stable/usa
### Check frequency
<span class="minilink minilink-addedin">New in version 1.6.2</span>
You can optionally configure checks to run on a periodic basis rather than
every time borgmatic runs checks. For instance:
<span class="minilink minilink-addedin">New in version 1.6.2</span> You can
optionally configure checks to run on a periodic basis rather than every time
borgmatic runs checks. For instance:
```yaml
consistency:

View file

@ -53,11 +53,10 @@ borgmatic info
### Searching for a file
<span class="minilink minilink-addedin">New in version 1.6.3</span>
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`:
<span class="minilink minilink-addedin">New in version 1.6.3</span> 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

View file

@ -137,12 +137,11 @@ YAML limitation.)
### Deep merge
<span class="minilink minilink-addedin">New in version 1.6.0</span>
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
<span class="minilink minilink-addedin">New in version 1.6.0</span> 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.

View file

@ -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.
<span class="minilink minilink-addedin">New in version 1.6.4</span>
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:
<span class="minilink minilink-addedin">New in version 1.6.4</span> 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: