diff options
Diffstat (limited to 'doc/tips/what_to_do_when_you_lose_a_repository/comment_9_525e58e5941220b23b0ed73fa7611db1._comment')
| -rw-r--r-- | doc/tips/what_to_do_when_you_lose_a_repository/comment_9_525e58e5941220b23b0ed73fa7611db1._comment | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/tips/what_to_do_when_you_lose_a_repository/comment_9_525e58e5941220b23b0ed73fa7611db1._comment b/doc/tips/what_to_do_when_you_lose_a_repository/comment_9_525e58e5941220b23b0ed73fa7611db1._comment new file mode 100644 index 000000000..a91793568 --- /dev/null +++ b/doc/tips/what_to_do_when_you_lose_a_repository/comment_9_525e58e5941220b23b0ed73fa7611db1._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2016-05-03T19:15:58Z" + content=""" +Both `git annex sync` and `git pull` will still try to access the git +remote for the repository. Thing to do to prevent this is `git remote +remove` it. + +I think it makes sense for `git annex sync` to still try to push/pull +from a dead remote, since git pull/push will still try to access it +too. Marking the remote dead does prevent other git-annex commands +from trying to use it for data storage. +"""]] |