From a6edd94e3e5d1e5c33fbf56c7bb88615930bb0af Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 10 Nov 2012 19:48:01 +0000 Subject: [PATCH 1/3] Added a comment --- ...mment_4_e51d6f854db5f9e74a1aa58bd8923795._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/design/assistant/blog/day_114__xmpp/comment_4_e51d6f854db5f9e74a1aa58bd8923795._comment diff --git a/doc/design/assistant/blog/day_114__xmpp/comment_4_e51d6f854db5f9e74a1aa58bd8923795._comment b/doc/design/assistant/blog/day_114__xmpp/comment_4_e51d6f854db5f9e74a1aa58bd8923795._comment new file mode 100644 index 0000000000..7320d03654 --- /dev/null +++ b/doc/design/assistant/blog/day_114__xmpp/comment_4_e51d6f854db5f9e74a1aa58bd8923795._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.152.108.27" + subject="comment 4" + date="2012-11-10T19:48:01Z" + content=""" +I hadn't tried it, but it looks like a very good idea. I will have to change my protocol a little bit as I currently sometimes send chat messages not directed to a specific client, in order to reach any clients using an account. To reach clients with a negative priority, chat messages have to be directed at the client. + +Ok, done; priority is set to -1 and all the XMPP messaging in git-annex still seems to work! + +I don't know though, that this entirely solves the problem. In particular, a regular xmpp client may decide to direct a chat message at a git-annex client, due to that being the only client connected. If this does become a problem, I suppose git-annex could buffer and re-send such messages when it sees a regular client connect. Or it could show them in the webapp, but that seems feature creep. +"""]] From ff7810eb83d8372e6206d487c63482d678e0b3d4 Mon Sep 17 00:00:00 2001 From: "http://phil.0x539.de/" Date: Sat, 10 Nov 2012 20:19:34 +0000 Subject: [PATCH 2/3] poll vote (Amazon Glacier) --- doc/design/assistant/polls/prioritizing_special_remotes.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn index 22cfa84d77..2f7f4bc72a 100644 --- a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn +++ b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn @@ -6,7 +6,7 @@ locally paired systems, and remote servers with rsync. Help me prioritize my work: What special remote would you most like to use with the git-annex assistant? -[[!poll open=yes 15 "Amazon S3 (done)" 10 "Amazon Glacier" 8 "Box.com" 61 "My phone (or MP3 player)" 15 "Tahoe-LAFS" 5 "OpenStack SWIFT" 23 "Google Drive"]] +[[!poll open=yes 15 "Amazon S3 (done)" 11 "Amazon Glacier" 8 "Box.com" 61 "My phone (or MP3 player)" 15 "Tahoe-LAFS" 5 "OpenStack SWIFT" 23 "Google Drive"]] This poll is ordered with the options I consider easiest to build listed first. Mostly because git-annex already supports them and they From 0fe0cb20c8bdafc0801cfd2417e08dfc01c8bf5a Mon Sep 17 00:00:00 2001 From: "http://phil.0x539.de/" Date: Sat, 10 Nov 2012 21:40:22 +0000 Subject: [PATCH 3/3] --- doc/bugs/creds_directory_not_automatically_created.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/bugs/creds_directory_not_automatically_created.mdwn diff --git a/doc/bugs/creds_directory_not_automatically_created.mdwn b/doc/bugs/creds_directory_not_automatically_created.mdwn new file mode 100644 index 0000000000..0aaa9b0be8 --- /dev/null +++ b/doc/bugs/creds_directory_not_automatically_created.mdwn @@ -0,0 +1 @@ +I just compiled ff7810eb83d8372e6206d487c63482d678e0b3d4 and created a new git-annex repository through the setup steps of "git-annex webapp". Then I tried configuring a Jabber account from the webapp. It then failed to create $REPO/.git/annex/creds/xmpp with a "No such file or directory" message because $REPO/.git/annex/creds did not get created. After doing a manual mkdir the Jabber setup went through fine.