diff options
| -rw-r--r-- | doc/tips/what_to_do_when_you_lose_a_repository/comment_8_596bcfa25a4fa6e81bb6a0940c55a2f2._comment | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_you_lose_a_repository/comment_8_596bcfa25a4fa6e81bb6a0940c55a2f2._comment b/doc/tips/what_to_do_when_you_lose_a_repository/comment_8_596bcfa25a4fa6e81bb6a0940c55a2f2._comment new file mode 100644 index 000000000..addeccbf5 --- /dev/null +++ b/doc/tips/what_to_do_when_you_lose_a_repository/comment_8_596bcfa25a4fa6e81bb6a0940c55a2f2._comment @@ -0,0 +1,7 @@ +[[!comment format=mdwn + username="fiatjaf" + subject="comment 8" + date="2016-04-23T15:01:23Z" + content=""" +I've issued `git annex dead` for a full git-annex repo (not a special remote) I had in a VPS, but my local machine keeps trying to sync with it on `git annex sync`, asking me to confirm the ssh public key and so on. Is that correct? +"""]] |