From 3b155dd32d6f70bcc7ebe56ff56e82dc9be05627 Mon Sep 17 00:00:00 2001 From: jarno Date: Tue, 14 Aug 2018 16:03:39 +0000 Subject: [PATCH] Added a comment --- .../comment_2_7d0e219628ad19093c6b6410d24c5f9a._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Forcing_offline_copies_seem_available/comment_2_7d0e219628ad19093c6b6410d24c5f9a._comment diff --git a/doc/forum/Forcing_offline_copies_seem_available/comment_2_7d0e219628ad19093c6b6410d24c5f9a._comment b/doc/forum/Forcing_offline_copies_seem_available/comment_2_7d0e219628ad19093c6b6410d24c5f9a._comment new file mode 100644 index 0000000000..a63102f62e --- /dev/null +++ b/doc/forum/Forcing_offline_copies_seem_available/comment_2_7d0e219628ad19093c6b6410d24c5f9a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="jarno" + avatar="http://cdn.libravatar.org/avatar/da157278ab330a9c936dd733c43740f8" + subject="comment 2" + date="2018-08-14T16:03:39Z" + content=""" +Nice, thank you! I think I'll just delete or move the proxy away after feeding the (fake) availability info to the main repo. That should prevent git-annex from accidentally discovering that the data doesn't actually exist on the proxy, right? +"""]]