summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar tanen <tanen@web>2015-08-23 20:34:20 +0000
committerGravatar admin <admin@branchable.com>2015-08-23 20:34:20 +0000
commita61c7ea04c9ba27d0c3cba98dfa20851d6945e6e (patch)
tree85c19d118c411eb223a559fd9797ad36eb620f6a
parent6759ec26aa78596c8d7f4d613878fc4e748fb42a (diff)
Added a comment
-rw-r--r--doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_15_de4838d82987685896d4c76dac7cdb6c._comment9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_15_de4838d82987685896d4c76dac7cdb6c._comment b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_15_de4838d82987685896d4c76dac7cdb6c._comment
new file mode 100644
index 000000000..3eb381206
--- /dev/null
+++ b/doc/tips/fully_encrypted_git_repositories_with_gcrypt/comment_15_de4838d82987685896d4c76dac7cdb6c._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="tanen"
+ subject="comment 15"
+ date="2015-08-23T20:34:20Z"
+ content="""
+I just created the same setup again that I attempted 1-2 years ago, with the latest self-contained git-annex build. Two clients, one SSH server, using gcrypt. Setup worked flawless now (although the process of having to manually export the generated GPG key and import it into all clients is still very awkward); changes made on a client are immediately detected and synced with the server. However, the changes made on client A are never automatically propagated to client B. They are picked up when I restart the annex assistant on client B, but never automatically.
+
+Is this a bug or simply not supported? I read about XMPP being deprecated in favor of notifications via the annex-shell, but I couldn't find a post detailing these changes.
+"""]]