From 79705f831bb623f957da0ce2e184f66ed75a3b7d Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Sat, 5 Oct 2019 02:47:10 +0000 Subject: [PATCH] fix typo --- ...k_git_from_pushing_references_to_not-yet-saved_contents.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents.mdwn b/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents.mdwn index b520f68b93..21b6e8d105 100644 --- a/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents.mdwn +++ b/doc/todo/option_to_block_git_from_pushing_references_to_not-yet-saved_contents.mdwn @@ -1,3 +1,3 @@ -One way I've lost data is to git-annex-add it in an untrusted temp clone of a repo, then commit and push the git branch, but forget to git-annex-copy the annexed contents reference by that branch to a GloballyAvailable, (semi-)trusted remote. Then, when the temp clone is gone, the branch pushed to the repo is referencing permanently dead files. Maybe, git-annex-init could install a pre-push hook to check for this, and abort the push if it happens? Basically, to ensure that whatever data is referenced by pushed branches will actually be at least potentially get-table. +One way I've lost data is to git-annex-add it in an untrusted temp clone of a repo, then commit and push the git branch, but forget to git-annex-copy the annexed contents referenced by that branch to a GloballyAvailable, (semi-)trusted remote. Then, when the temp clone is gone, the branch pushed to the repo is referencing permanently dead files. Maybe, git-annex-init could install a pre-push hook to check for this, and abort the push if it happens? Basically, to ensure that whatever data is referenced by pushed branches will actually be at least potentially get-table. Even if the current repo is not temp/untrusted, when sharing data with someone, you may want to ensure that any annexed files referenced by a pushed branch are actually potentially available.