summaryrefslogtreecommitdiff
path: root/doc/tips/Accessing_files_in_bare_remotes_without_git-annex
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-01-30 12:54:32 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-01-30 13:18:50 -0400
commit0b1a6e9ba0180f77d12895d7576dfc06238f5c51 (patch)
treef854d6f277e068afca9a90ae73db0a30075cde3c /doc/tips/Accessing_files_in_bare_remotes_without_git-annex
parentf81280a6e378b4350252ee68a897d4399dd9d2ac (diff)
reusing repository uuid cannot result in data loss AFAIK
Avoiding such problems is one reason why git-annex does active verification of other copies of a file when dropping. You could argue that reusing the uuid of a trusted repository leads to data loss, but that data loss doesn't really involve reusing the uuid, but instead is caused by deleting a trusted repository. Using trusted repositories without a great deal of care is a good way to blow off your foot, of which deleting them is only the most obvious; added some sections about that. If reusing a repository uuid could result in data loss then I'd be on board with making reinit run a fast fsck to update the location log, but since it can't, I feel that is not worth forcing. Not a bad idea to run fsck afterwards. Updated language about that. This commit was sponsored by Jake Vosloo on Patreon.
Diffstat (limited to 'doc/tips/Accessing_files_in_bare_remotes_without_git-annex')
0 files changed, 0 insertions, 0 deletions