mirror of https://github.com/restic/restic.git
Merge pull request #3468 from restic/rework-changelog
Reword changelog entries
This commit is contained in:
commit
b862732318
|
@ -1,14 +1,12 @@
|
|||
Bugfix: Improve error handling for rclone and rest backend over HTTP2
|
||||
Bugfix: Improve error handling for rclone and REST backend over HTTP2
|
||||
|
||||
When retrieving data from the rclone / rest backend while also using HTTP2
|
||||
When retrieving data from the rclone / REST backend while also using HTTP2
|
||||
restic did not detect when no data was returned at all. This could cause
|
||||
for example the `check` command to report the following error:
|
||||
```
|
||||
Pack ID does not match, want xxxxxxxx, got e3b0c442
|
||||
```
|
||||
|
||||
This has been fixed by correctly detecting the incomplete download and
|
||||
retrying the download.
|
||||
Pack ID does not match, want [...], got e3b0c442
|
||||
|
||||
This has been fixed by correctly detecting and retrying the incomplete download.
|
||||
|
||||
https://github.com/restic/restic/issues/2742
|
||||
https://github.com/restic/restic/pull/3453
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
Bugfix: Fix terminal output redirection for powershell
|
||||
Bugfix: Fix terminal output redirection for PowerShell
|
||||
|
||||
When redirecting the output of restic using powershell on Windows, the
|
||||
When redirecting the output of restic using PowerShell on Windows, the
|
||||
output contained terminal escape characters. This has been fixed by
|
||||
properly detecting the terminal type.
|
||||
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
Change: Empty files now have size of 0 in restic ls --json output
|
||||
Change: Empty files now have size of 0 in `ls --json` output
|
||||
|
||||
Restic ls --json used to omit the sizes of empty files in its output. It now
|
||||
reports "size":0 explicitly for regular files, while omitting the size field
|
||||
for all other types.
|
||||
The `ls --json` command used to omit the sizes of empty files in its
|
||||
output. It now reports a size of zero explicitly for regular files,
|
||||
while omitting the size field for all other types.
|
||||
|
||||
https://github.com/restic/restic/issues/3247
|
||||
https://github.com/restic/restic/pull/3257
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
Bugfix: Fix crash of `check --read-data-subset=x%` run for an empty repository
|
||||
|
||||
`check --read-data-subset=x%` crashed when run for an empty repository. This
|
||||
has been fixed.
|
||||
The command `restic check --read-data-subset=x%` crashed when run for an empty
|
||||
repository. This has been fixed.
|
||||
|
||||
https://github.com/restic/restic/issues/3296
|
||||
https://github.com/restic/restic/pull/3309
|
||||
|
|
|
@ -1,6 +1,5 @@
|
|||
Enhancement: Add auto-completion file for fish
|
||||
Enhancement: Add auto-completion support for fish
|
||||
|
||||
The version of cobra had been increased to v1.1.3, and `generate` command has added
|
||||
auto-completion file for fish.
|
||||
The `generate` command now supports fish auto completion.
|
||||
|
||||
https://github.com/restic/restic/pull/3312
|
||||
|
|
|
@ -1,9 +1,8 @@
|
|||
Bugfix: Print `created new cache` message only on a terminal
|
||||
|
||||
`created new cache` message was outputed even when the output wasn't a
|
||||
terminal. That broke piping `restic dump` output to tar or zip
|
||||
if cache directory didn't exist. The message is now only printed on a
|
||||
terminal.
|
||||
The message `created new cache` was printed even when the output wasn't a
|
||||
terminal. That broke piping `restic dump` output to tar or zip if cache
|
||||
directory didn't exist. The message is now only printed on a terminal.
|
||||
|
||||
https://github.com/restic/restic/issues/3334
|
||||
https://github.com/restic/restic/pull/3343
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
Enhancement: Add release binaries for Apple Silicon
|
||||
|
||||
We've added release binaries for macOS on Apple Silicon.
|
||||
We've added release binaries for macOS on Apple Silicon (M1).
|
||||
|
||||
https://github.com/restic/restic/issues/3377
|
||||
https://github.com/restic/restic/pull/3394
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
Bugfix: Fix crash of `backup --exclude='**'`
|
||||
|
||||
The exclude filter '**', which excludes all files, caused restic to crash. This
|
||||
has been fixed.
|
||||
The exclude filter `**`, which excludes all files, caused restic to crash. This
|
||||
has been corrected.
|
||||
|
||||
https://github.com/restic/restic/issues/3380
|
||||
https://github.com/restic/restic/pull/3393
|
||||
|
|
|
@ -1,19 +1,19 @@
|
|||
Enhancement: Add --keep-within-hourly switch to restic forget
|
||||
Enhancement: Add `--keep-within-hourly` option to restic forget
|
||||
|
||||
restic forget allowed users to specify keeping a given number of
|
||||
hourly backups, or to keep all backups within a given interval,
|
||||
but not both, that is to specify keeping hourly backups within
|
||||
a given interval.
|
||||
The `forget` command allowed keeping a given number of hourly
|
||||
backups or to keep all backups within a given interval, but it
|
||||
was not possible to specify keeping hourly backups within a given
|
||||
interval.
|
||||
|
||||
The --keep-within-hourly switch offers this functionality, and
|
||||
parallell switches for daily/weekly/monthly/yearly are also
|
||||
implemneted. The new switches are:
|
||||
The new `--keep-within-hourly` option now offers this functionality.
|
||||
Similar options for daily/weekly/monthly/yearly are also implemented,
|
||||
the new options are:
|
||||
|
||||
--keep-within-hourly <1y2m3d4h>
|
||||
--keep-within-daily <1y2m3d4h>
|
||||
--keep-within-weekly <1y2m3d4h>
|
||||
--keep-within-monthly <1y2m3d4h>
|
||||
--keep-within-yearly <1y2m3d4h>
|
||||
--keep-within-hourly <1y2m3d4h>
|
||||
--keep-within-daily <1y2m3d4h>
|
||||
--keep-within-weekly <1y2m3d4h>
|
||||
--keep-within-monthly <1y2m3d4h>
|
||||
--keep-within-yearly <1y2m3d4h>
|
||||
|
||||
https://github.com/restic/restic/issues/3414
|
||||
https://github.com/restic/restic/pull/3416
|
||||
|
|
|
@ -1,9 +1,9 @@
|
|||
Enhancement: Allow limiting the snapshots list
|
||||
Enhancement: Allow specifying limit of `snapshots` list
|
||||
|
||||
The `--last` option allowed limiting the output of the `snapshots`
|
||||
command to the latest snapshot for each host. The new `--latest n`
|
||||
option allows limiting the output to the latest `n` snapshots.
|
||||
|
||||
This change deprecate `--last` in favour of `--latest 1`
|
||||
This change deprecates the option `--last` in favour of `--latest 1`.
|
||||
|
||||
https://github.com/restic/restic/pull/3167
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
Bugfix: Fix possibly missing backup summary of json output in case of error
|
||||
Bugfix: Fix possibly missing backup summary of JSON output in case of error
|
||||
|
||||
When using --json output it happened from time to time that the summary output
|
||||
was missing in case an error occurred. This has been fixed.
|
||||
When using `--json` output it happened from time to time that the summary
|
||||
output was missing in case an error occurred. This has been fixed.
|
||||
|
||||
https://github.com/restic/restic/pull/3305
|
||||
|
|
|
@ -1,10 +1,10 @@
|
|||
Enhancement: `find --pack` fallback to index if data file is missing
|
||||
|
||||
When investigating a repository with missing data files, it might be useful
|
||||
to determine affected snapshots before running `rebuild-index`.
|
||||
`restic find --pack pack-id` previously returned no data as it required
|
||||
accessing the data file. Now, if the necessary data is still available in the
|
||||
repository index, it gets retrieved from there.
|
||||
When investigating a repository with missing data files, it might be useful to
|
||||
determine affected snapshots before running `rebuild-index`. Previously,
|
||||
`find --pack pack-id` returned no data as it required accessing the data file.
|
||||
Now, if the necessary data is still available in the repository index, it gets
|
||||
retrieved from there.
|
||||
|
||||
The command now also supports looking up multiple pack files in a single `find`
|
||||
run.
|
||||
|
|
|
@ -1,8 +1,8 @@
|
|||
Bugfix: Correctly handle download errors during `restore`
|
||||
|
||||
Due to a regression in restic 0.12.0 the `restore` command in some cases
|
||||
did not retry download errors and only printed a warning. This has been
|
||||
fixed by retrying incomplete data downloads.
|
||||
Due to a regression in restic 0.12.0, the `restore` command in some cases did
|
||||
not retry download errors and only printed a warning. This has been fixed by
|
||||
retrying incomplete data downloads.
|
||||
|
||||
https://github.com/restic/restic/issues/3439
|
||||
https://github.com/restic/restic/pull/3449
|
||||
|
|
Loading…
Reference in New Issue