mirror of
https://github.com/restic/restic.git
synced 2026-11-21 13:02:42 +00:00
polish changelogs
This commit is contained in:
1 parent
df8454770b
commit
f058670219
5 files changed
+14
-15
No files matched your search
@@ -1,8 +1,8 @@
|
|||||||
Bugfix: Hide progress bar for stats command in JSON mode
|
Bugfix: Hide progress bar for `stats` in JSON mode
|
||||||
|
|
||||||
Since restic 0.19.0, the stats command shows a progress bar. However,
|
Since restic 0.19.0, the `stats` command shows a progress bar. However,
|
||||||
it was also active when given the `--json` option resulting in text
|
it was also active with the `--json` option, which mixed text output with
|
||||||
mixed with JSON. This has been fixed.
|
JSON. This has been fixed.
|
||||||
|
|
||||||
https://github.com/restic/restic/issues/21866
|
https://github.com/restic/restic/issues/21866
|
||||||
https://github.com/restic/restic/pull/21871
|
https://github.com/restic/restic/pull/21871
|
||||||
@@ -3,9 +3,9 @@ Bugfix: Restore old behavior of `snapshots --latest <n>` without `--group-by`
|
|||||||
Restic 0.19.0 changed the behavior of `snapshots --latest <n>` to no longer
|
Restic 0.19.0 changed the behavior of `snapshots --latest <n>` to no longer
|
||||||
group snapshots by default.
|
group snapshots by default.
|
||||||
|
|
||||||
`snapshots --latest <n>` has been reverted to the old behavior if `--group-by`
|
`snapshots --latest <n>` again uses the old behavior when `--group-by` is not
|
||||||
is not specified. When specifying `--group-by`, the output is still grouped as
|
specified. With `--group-by`, the output is still grouped as requested, as in
|
||||||
requested like in restic 0.19.0.
|
restic 0.19.0.
|
||||||
|
|
||||||
https://github.com/restic/restic/issues/21869
|
https://github.com/restic/restic/issues/21869
|
||||||
https://github.com/restic/restic/pull/21875
|
https://github.com/restic/restic/pull/21875
|
||||||
@@ -1,9 +1,8 @@
|
|||||||
Bugfix: Fix excludes of duplicate directory entries during `backup`
|
Bugfix: Respect excludes for duplicate directory entries during `backup`
|
||||||
|
|
||||||
Since restic 0.19.0, creating a backup of a directory containing
|
Since restic 0.19.0, backing up a directory with duplicate directory
|
||||||
duplicate directory entries always resulted in "Warning: at least
|
entries always produced "Warning: at least one source file could not be
|
||||||
one source file could not be read" even if the files in question
|
read" even when those files were excluded. This has been fixed.
|
||||||
were excluded. This has been fixed.
|
|
||||||
|
|
||||||
https://github.com/restic/restic/issues/21899
|
https://github.com/restic/restic/issues/21899
|
||||||
https://github.com/restic/restic/pull/21900
|
https://github.com/restic/restic/pull/21900
|
||||||
@@ -1,8 +1,8 @@
|
|||||||
Bugfix: Show timezone location in `snapshots` output
|
Bugfix: Show timezone location in `snapshots` output
|
||||||
|
|
||||||
Since restic 0.19.0, the `snapshots` command printed the current timezone when
|
Since restic 0.19.0, the `snapshots` command printed the current timezone when
|
||||||
listing snapshots. However, the timezone can change during the year, for example,
|
listing snapshots. That label can change during the year, for example with
|
||||||
due to daylight saving time. Instead just print the name of the current location.
|
daylight saving time. Restic now prints the location name instead.
|
||||||
|
|
||||||
https://github.com/restic/restic/pull/21876
|
https://github.com/restic/restic/pull/21876
|
||||||
https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
|
https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
|
||||||
@@ -1,4 +1,4 @@
|
|||||||
Bugfix: prevent crash in mountpoint validation if mountpoint is inaccessible
|
Bugfix: Prevent crash in mountpoint validation if mountpoint is inaccessible
|
||||||
|
|
||||||
Since restic 0.19.0, the `mount` command validates a mountpoint before loading
|
Since restic 0.19.0, the `mount` command validates a mountpoint before loading
|
||||||
the repository. If restic was unable to stat the mountpoint, this would result
|
the repository. If restic was unable to stat the mountpoint, this would result
|
||||||
|
|||||||
Reference in new issue
Block a user