aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Horus <Horus@web>2018-02-28 09:27:26 +0000
committerGravatar admin <admin@branchable.com>2018-02-28 09:27:26 +0000
commitcd572e9c2b0a0025de015cef48f3a8cb04fd030c (patch)
treea71373a2a9fef42b11bc21469201e68b18609194
parent7500c8e6cb0695b52bab24bd88b5e806f148832d (diff)
-rw-r--r--doc/forum/Auto_ignore_non-reachable_repo.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/Auto_ignore_non-reachable_repo.mdwn b/doc/forum/Auto_ignore_non-reachable_repo.mdwn
new file mode 100644
index 000000000..c56872536
--- /dev/null
+++ b/doc/forum/Auto_ignore_non-reachable_repo.mdwn
@@ -0,0 +1,15 @@
+Hello,
+
+having multiple remotes, which are often unreachable, I get command output like:
+
+ git annex drop .
+ drop 2017 Haus Idstein/26108065_10212412239435248_1115645256_o.jpg (locking horus...) (lockcontent failed) (checking horus...) ssh: Could not resolve hostname horus.local: Name or service not known
+ (checking S3...) ok
+ drop 2017 Haus Idstein/26177516_10212412238475224_326557077_o.jpg (locking horus...) (lockcontent failed) (checking horus...) ssh: Could not resolve hostname horus.local: Name or service not known
+ (checking S3...) ok
+ drop 2017 Haus Idstein/26178378_10212412238835233_820819105_o.jpg (locking horus...) (lockcontent failed) (checking horus...) ssh: Could not resolve hostname horus.local: Name or service not known
+ (checking S3...) ok
+
+which takes a long time, because it tries to lock horus first for each, waits for timeout and then tries the next remote. Of course I could use ```git annex drop --from=S3``` but I do not always remember that. Is there a way to auto ignore a remote which is not reachable?
+
+Thanks!