aboutsummaryrefslogtreecommitdiff
path: root/Assistant
Commit message (Collapse)AuthorAge
* The standalone builds now unset their special path and library path ↵Gravatar Joey Hess2012-11-27
| | | | | | variables before running the system web browser. Should fix a crash reported on OSX.
* allow building webapp w/o webdavGravatar Joey Hess2012-11-25
|
* webapp and assistant glacier supportGravatar Joey Hess2012-11-24
|
* queue uploads when a new or renamed symlink is handledGravatar Joey Hess2012-11-24
|
* webapp: support box.comGravatar Joey Hess2012-11-17
|
* update to dav 0.1, and basic uploading is working!Gravatar Joey Hess2012-11-15
|
* factor out CredsGravatar Joey Hess2012-11-14
|
* use System.TimeoutGravatar Joey Hess2012-11-14
| | | | I'd forgotten this existed!
* automatic repolist updatingGravatar Joey Hess2012-11-13
|
* Fix build of assistant without yesod.Gravatar Joey Hess2012-11-13
|
* upper-case first char of buddy nameGravatar Joey Hess2012-11-12
|
* add a yes/no confirm for xmpp pairing requestsGravatar Joey Hess2012-11-11
|
* auto-accept pair requests from JIDs already paired withGravatar Joey Hess2012-11-11
|
* don't try to transfer data to/from XMPP remotesGravatar Joey Hess2012-11-11
| | | | | Partition syncRemotes into ones needing git sync (ie, non-special remotes), and ones needing data sync (ie, non-XMPP remotes).
* allow both one push and one receive-pack to run at the same timeGravatar Joey Hess2012-11-11
| | | | | | Noticed that when pairing, sometimes both sides start to push, and the other side sends a PushRequest, and the two deadlock, neither doing anything. (Timeout eventually breaks this.) So, let both run at the same time.
* add 120 second timeout when waiting for XMPP packetsGravatar Joey Hess2012-11-11
|
* use trustExcludeGravatar Joey Hess2012-11-11
|
* reword alertGravatar Joey Hess2012-11-10
|
* fix creation of creds directory for xmppGravatar Joey Hess2012-11-10
|
* show when a buddy is already pairedGravatar Joey Hess2012-11-10
|
* set negative XMPP presence priorityGravatar Joey Hess2012-11-10
| | | | | | | | This should help prevent git-annex clients receiving messages that were intended for normal clients they're sharing the account with. Changed XMPP protocol use to always send chat messages directed at the specific client, as the negative priority blocks less directed messages.
* avoid sending xmpp push notifications when not pushing to any remotesGravatar Joey Hess2012-11-10
|
* full-on git-annex assistant syncing now works over XMPP!Gravatar Joey Hess2012-11-10
| | | | | | | | | | I decided to use the fallback push mode from the beginning for XMPP, since while it uses some ugly branches, it avoids the possibility of a normal push failing, and needing to pull and re-push. Due to the overhead of XMPP, and the difficulty of building such a chain of actions due to the async implementation, this seemed reasonable. It seems to work great!
* more refactoringGravatar Joey Hess2012-11-10
|
* more nice refactoringGravatar Joey Hess2012-11-10
|
* better data types allowed marvelous refactoringGravatar Joey Hess2012-11-10
|
* separate data type for push stagesGravatar Joey Hess2012-11-10
| | | | This improves type safety.
* refactorGravatar Joey Hess2012-11-10
|
* use a lookup table for speedGravatar Joey Hess2012-11-10
|
* on second thought, do allow deferring StartingPushGravatar Joey Hess2012-11-10
| | | | | | My reasoning is that StartingPush could be received after another push starts being received, and it would be better to respond to it afterwards than not.
* refactorGravatar Joey Hess2012-11-10
|
* fix deferring of CanPush, and stop deferring StartingPushGravatar Joey Hess2012-11-10
|
* refactorGravatar Joey Hess2012-11-10
|
* refactorGravatar Joey Hess2012-11-10
|
* refactorGravatar Joey Hess2012-11-10
|
* fix exit code propigationGravatar Joey Hess2012-11-10
|
* refactorGravatar Joey Hess2012-11-09
|
* ensure handles get closedGravatar Joey Hess2012-11-09
|
* increase chunk sizeGravatar Joey Hess2012-11-09
| | | | | | XMPP has no defined message size limits, but some servers will have ad-hoc limits. However, 4k seems safe, even after the additional bloat of base64. That should not exceed 8k.
* refactorGravatar Joey Hess2012-11-09
|
* refactorGravatar Joey Hess2012-11-09
|
* avoid excessive debuggingGravatar Joey Hess2012-11-09
|
* xmpp git push is working!Gravatar Joey Hess2012-11-09
| | | | | | Various final bug fixes, and tweaks that got it working. Currently pushes a hardcoded ref, which needs to be fixed, etc.
* fix murderous typoGravatar Joey Hess2012-11-09
|
* run xmpp push actions in separate thread from xmpp clientGravatar Joey Hess2012-11-09
| | | | | Took me a while to figure out why the xmpp client was not receiving git xmpp push messages after a push started.
* fix git push startupGravatar Joey Hess2012-11-09
|
* add canpush xmpp commandGravatar Joey Hess2012-11-09
|
* use xmpp::user@host for xmpp remotesGravatar Joey Hess2012-11-09
| | | | | | Inject the required git-remote-xmpp into PATH when running xmpp git push. Rest of the time it will not be in PATH, and git won't be able to talk to xmpp remotes.
* blog for the dayGravatar Joey Hess2012-11-08
|
* xmpp push control flowGravatar Joey Hess2012-11-08
| | | | | | | | | It might even work, although nothing yet triggers XMPP pushes. Also added a set of deferred push messages. Only one push can run at a time, and unrelated push messages get deferred. The set will never grow very large, because it only puts two types of messages in there, that can only vary in the client doing the push.