mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update

Browse source
This commit is contained in:
Joey Hess 2013-04-30 16:57:40 -04:00
parent e363cefcb3
commit 6e93a8d292
2 changed files with 1 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/xmpp_needs_one_account_per_distinct_repository.mdwn
View file

@ -85,7 +85,7 @@ So, we need another fix:
* Send UUID in XMPP git push protocol messages. Only respond to git push * Send UUID in XMPP git push protocol messages. Only respond to git push
messages from a known UUID, and ignore all others. (XMPP pairing messages from a known UUID, and ignore all others. (XMPP pairing
already sends the UUID, so it will be known.) already sends the UUID, so it will be known.) **done**
---- ----

10
doc/design/assistant/xmpp.mdwn
View file

@ -10,16 +10,6 @@ who share a repository, that is stored in the [[cloud]].
things to happen? things to happen?
See <http://git-annex.branchable.com/design/assistant/blog/day_114__xmpp/#comment-aaba579f92cb452caf26ac53071a6788> See <http://git-annex.branchable.com/design/assistant/blog/day_114__xmpp/#comment-aaba579f92cb452caf26ac53071a6788>
* Support use of a single XMPP account with several separate and
independant git-annex repos. This probably works for the simple
push notification use of XMPP, since unknown UUIDs will just be ignored.
But XMPP pairing and the pushes over XMPP assume that anyone you're
paired with is intending to sync to your repository.
[[bugs/xmpp_needs_one_account_per_distinct_repository]]
There are really two cases here, "Share with your other devices",
and
## design goals ## design goals
1. Avoid user-visible messages. dvcs-autosync uses XMPP similarly, but 1. Avoid user-visible messages. dvcs-autosync uses XMPP similarly, but