From f058670219310cfe74fcbec841fbe2191da0e76f Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Tue, 23 Jun 2026 19:54:47 +0200 Subject: [PATCH] polish changelogs --- changelog/unreleased/issue-21866 | 8 ++++---- changelog/unreleased/issue-21869 | 6 +++--- changelog/unreleased/issue-21899 | 9 ++++----- changelog/unreleased/pull-21876 | 4 ++-- changelog/unreleased/pull-21879 | 2 +- 5 files changed, 14 insertions(+), 15 deletions(-) diff --git a/changelog/unreleased/issue-21866 b/changelog/unreleased/issue-21866 index 815a472c1..5e4019778 100644 --- a/changelog/unreleased/issue-21866 +++ b/changelog/unreleased/issue-21866 @@ -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, -it was also active when given the `--json` option resulting in text -mixed with JSON. This has been fixed. +Since restic 0.19.0, the `stats` command shows a progress bar. However, +it was also active with the `--json` option, which mixed text output with +JSON. This has been fixed. https://github.com/restic/restic/issues/21866 https://github.com/restic/restic/pull/21871 diff --git a/changelog/unreleased/issue-21869 b/changelog/unreleased/issue-21869 index 774c5e4d1..a0389adfa 100644 --- a/changelog/unreleased/issue-21869 +++ b/changelog/unreleased/issue-21869 @@ -3,9 +3,9 @@ Bugfix: Restore old behavior of `snapshots --latest ` without `--group-by` Restic 0.19.0 changed the behavior of `snapshots --latest ` to no longer group snapshots by default. -`snapshots --latest ` has been reverted to the old behavior if `--group-by` -is not specified. When specifying `--group-by`, the output is still grouped as -requested like in restic 0.19.0. +`snapshots --latest ` again uses the old behavior when `--group-by` is not +specified. With `--group-by`, the output is still grouped as requested, as in +restic 0.19.0. https://github.com/restic/restic/issues/21869 https://github.com/restic/restic/pull/21875 diff --git a/changelog/unreleased/issue-21899 b/changelog/unreleased/issue-21899 index 1eceba1d9..7181cd1ad 100644 --- a/changelog/unreleased/issue-21899 +++ b/changelog/unreleased/issue-21899 @@ -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 -duplicate directory entries always resulted in "Warning: at least -one source file could not be read" even if the files in question -were excluded. This has been fixed. +Since restic 0.19.0, backing up a directory with duplicate directory +entries always produced "Warning: at least one source file could not be +read" even when those files were excluded. This has been fixed. https://github.com/restic/restic/issues/21899 https://github.com/restic/restic/pull/21900 diff --git a/changelog/unreleased/pull-21876 b/changelog/unreleased/pull-21876 index ec8e2d8f1..9e19d1858 100644 --- a/changelog/unreleased/pull-21876 +++ b/changelog/unreleased/pull-21876 @@ -1,8 +1,8 @@ Bugfix: Show timezone location in `snapshots` output 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, -due to daylight saving time. Instead just print the name of the current location. +listing snapshots. That label can change during the year, for example with +daylight saving time. Restic now prints the location name instead. https://github.com/restic/restic/pull/21876 https://forum.restic.net/t/possible-bug-in-timezone-naming/10867 diff --git a/changelog/unreleased/pull-21879 b/changelog/unreleased/pull-21879 index a64a4900f..f3b1aa229 100644 --- a/changelog/unreleased/pull-21879 +++ b/changelog/unreleased/pull-21879 @@ -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 the repository. If restic was unable to stat the mountpoint, this would result