Reword ten sentences after rereading the last commit's prose
check / check (push) Successful in 10m56s
check / check (push) Successful in 10m56s
The last commit was not written on the model that #397 requires. Every sentence it added or changed was read again under that issue's rules and checked against the code, as #399 (comment) asks. - The local index lists files too, so the README and the help text no longer say the file list is stored only in the snapshot's database. - The root help lists the three commands that need the private key. - The quoted-path, mode and rclone upload sentences now put the subject and verb early. - `docs/REPOSTRUCTURE.md` names the path that `snapshot files` writes. - The example config says what runs when the `snapshots` requirement is not met. - "take that object for complete" becomes "treat that object as complete". Model: fable-5-2
This commit is contained in:
1 parent
7b0f0e1362
commit
a3dfe94c8b
5 files changed
+25
-20
No files matched your search
@@ -312,7 +312,8 @@ These commands write unencrypted data to the temporary directory:
|
||||
is no limit on their total size.
|
||||
- `snapshot restore` writes the decrypted database to
|
||||
`vaultik-restore-*/snapshot.db`.
|
||||
- `snapshot files` writes the decrypted database to the same place.
|
||||
- `snapshot files` writes the decrypted database to
|
||||
`vaultik-restore-*/snapshot.db` as well.
|
||||
- `snapshot verify --deep` writes the decrypted database to
|
||||
`vaultik-verify-*/snapshot.db`.
|
||||
- `snapshot create` writes a copy of the local index to
|
||||
@@ -342,9 +343,9 @@ it needs no other permission. Other commands need more:
|
||||
- `prune` lists, reads and deletes.
|
||||
|
||||
On an rclone remote, a backup can also need permission to read and delete. Which
|
||||
ones depends on the storage service. An upload to a remote that can move objects
|
||||
looks up the object it replaces and deletes it. It stops when the look-up is
|
||||
refused.
|
||||
ones depends on the storage service. On a remote that can move objects, an
|
||||
upload looks up the object it replaces and deletes that object. The upload stops
|
||||
when the look-up is refused.
|
||||
|
||||
These commands list only when they are given a remote key, or a snapshot ID that
|
||||
is not in the local index:
|
||||
|
||||
Reference in new issue
Block a user