From 693d2cd23c19a08e7bd5cfca2d634d17be8a2394 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 18 Nov 2016 11:40:52 -0400 Subject: comment --- .../comment_1_0b523b2b6c361346c36ad456bbbac645._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/What_to_do_if_special_remotes_refuses_drops__63__/comment_1_0b523b2b6c361346c36ad456bbbac645._comment diff --git a/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__/comment_1_0b523b2b6c361346c36ad456bbbac645._comment b/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__/comment_1_0b523b2b6c361346c36ad456bbbac645._comment new file mode 100644 index 000000000..cf808aac4 --- /dev/null +++ b/doc/forum/What_to_do_if_special_remotes_refuses_drops__63__/comment_1_0b523b2b6c361346c36ad456bbbac645._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-11-18T15:39:20Z" + content=""" +It could certianly be a bug in the special remote implementation. It's also +possible for some special remotes to intentionally not be able to remove +content (this is the case with the web special remote, and the bup special +remote at least). + +You can manually remove the special remote, by editing .git/config and +deleting the stanza for that remote. You may want to run `git annex dead +$remotename` first, if you don't intend to ever use that special remote +again. +"""]] -- cgit v1.2.3