mirror of
https://github.com/octoleo/restic.git
synced 2024-12-22 10:58:55 +00:00
tweak changelogs
This commit is contained in:
parent
f342db7666
commit
1e6e9f9bd0
@ -1,9 +1,9 @@
|
||||
Bugfix: Exotic filenames no longer break restic backup's status output
|
||||
|
||||
Restic backup shows the names of files that it is working on. In previous
|
||||
Restic `backup` shows the names of files that it is working on. In previous
|
||||
versions of restic, those names were printed without first sanitizing them,
|
||||
so that filenames containing newlines or terminal control characters could
|
||||
mess up restic backup's output or even change the state of a terminal.
|
||||
mangle the status output or even change the state of a terminal.
|
||||
|
||||
Filenames are now checked and quoted if they contain non-printable or
|
||||
non-Unicode characters.
|
||||
|
@ -1,8 +1,8 @@
|
||||
Bugfix: Restic dump now interprets --host and --path correctly
|
||||
Bugfix: Make `dump` interpret --host and --path correctly
|
||||
|
||||
Restic dump previously confused its --host=<host> and --path=<path>
|
||||
options: it looked for snapshots with paths called <host> from hosts
|
||||
called <path>. It now treats the options as intended.
|
||||
A regression in restic 0.15.0 caused `dump` to confuse its `--host=<host>` and
|
||||
`--path=<path>` options: it looked for snapshots with paths called `<host>`
|
||||
from hosts called `<path>`. It now treats the options as intended.
|
||||
|
||||
https://github.com/restic/restic/issues/4211
|
||||
https://github.com/restic/restic/pull/4212
|
||||
|
@ -1,8 +1,8 @@
|
||||
Bugfix: Correct number of blocks reported in mount point
|
||||
|
||||
Restic mount points incorrectly reported the number of 512-byte (POSIX
|
||||
standard) blocks for files and links, due to a rounding bug. In particular,
|
||||
empty files were reported as taking one block instead of zero.
|
||||
Restic mount points reported and incorrect number of 512-byte (POSIX standard)
|
||||
blocks for files and links due to a rounding bug. In particular, empty files
|
||||
were reported as taking one block instead of zero.
|
||||
|
||||
The rounding is now fixed: the number of blocks reported is the file size
|
||||
(or link target size), divided by 512 and rounded up to a whole number.
|
||||
|
@ -1,11 +1,10 @@
|
||||
Bugfix: Mount command should no longer create spurious filesystem loops
|
||||
Bugfix: `mount` should no longer create spurious filesystem loops
|
||||
|
||||
When a backup contains a directory that has the same name as its parent,
|
||||
say, a/b/b, and the GNU find command were run on this backup in a restic
|
||||
mount, find command would refuse to traverse the lowest "b" directory,
|
||||
instead printing "File system loop detected". This is due to the way the
|
||||
restic mount command generates inode numbers for directories in the mount
|
||||
point.
|
||||
When a backup contains a directory that has the same name as its parent, say
|
||||
`a/b/b`, and the GNU `find` command were run on this backup in a restic mount,
|
||||
`find` would refuse to traverse the lowest `b` directory, instead printing
|
||||
`File system loop detected`. This is due to the way the restic mount command
|
||||
generates inode numbers for directories in the mount point.
|
||||
|
||||
The rule for generating these inode numbers was changed in 0.15.0. It has
|
||||
now been changed again to avoid this issue. A perfect rule does not exist,
|
||||
|
@ -1,5 +1,5 @@
|
||||
Enhancement: Add release binaries for riscv64 architecture on Linux
|
||||
|
||||
We've added release binaries for riscv64 architecture on Linux.
|
||||
We've added release binaries for the riscv64 architecture on Linux.
|
||||
|
||||
https://github.com/restic/restic/pull/4180
|
||||
|
@ -1,5 +1,5 @@
|
||||
Enhancement: Upgrade Minio to 7.0.49
|
||||
|
||||
Upgraded to allow use of the ap-southeast-4 region (Melbourne)
|
||||
Upgraded to allow use of the ap-southeast-4 region (Melbourne).
|
||||
|
||||
https://github.com/restic/restic/pull/4219
|
||||
|
Loading…
Reference in New Issue
Block a user