rawtaz
rawtaz
Is borg's `--one-file-system` different from restic's `--one-file-system` (that already exists for the `backup` command)?
I was just about to write that the suggested `--map-device-id` is way too complicated, @MichaelEischer beat me to it :D :+1:
For `backup`, the blobs in which your data in the repository are stored when backing up *are* already saved with a name that corresponds to the checksum of the data...
Right, understood. So, what problem does this solve? If the verification of those ten different parts of the file is good, then what you want to check is basically that...
You understood me better than I explained it :) When having to go through the dialog to allow the/a cert, I find that I most often need to wait one...
Preferrably after #4 :)
Sorry that it doesn't have it, and if that frustrates you, but repeating the same thing again and in a way that can come across as negative and somewhat demanding...
Please see the restic roadmap at https://forum.restic.net/t/roadmap-for-restic-0-17-to-0-19 and also the activity in the restic repository. You will see that work is going on with other and larger refactoring as well...
You are describing a different use case. This issue is only about telling restic that the next snapshot should contain what's in the backup set at this point in time,...
> From what I understood of your use case, you want to maintain the tree of the previous snapshot (--parent snapshot), and add only new files in the repository. You...