| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
This is so git remotes on servers without git-annex installed can be used
to keep clients' git repos in sync.
This is a behavior change, but since annex-sync can be set to disable
syncing with a remote, I think it's acceptable.
|
|
|
|
| |
network, or connecting a drive.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
All temporary and old functions are removed.
|
|
|
|
|
|
| |
Currently have three old versions of functions that more reworking is
needed to remove: getDaemonStatusOld, modifyDaemonStatusOld_, and
modifyDaemonStatusOld
|
|
|
|
| |
lots of nice cleanups
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Converted several threads to run in the monad.
Added a lot of useful combinators for working with the monad.
Now the monad includes the name of the thread.
Some debugging messages are disabled pending converting other threads.
|
|\
| |
| |
| |
| | |
Conflicts:
Assistant/Threads/NetWatcher.hs
|
| |
| |
| |
| |
| |
| |
| |
| | |
MountWatcher can't do this, because it uses the session dbus,
and won't have access to the new DBUS_SESSION_BUS_ADDRESS if a new session
is started.
Bumped dbus library version, FD leak in it is fixed.
|
|\|
| |
| |
| |
| |
| | |
Conflicts:
Assistant/Threads/MountWatcher.hs
Assistant/Threads/NetWatcher.hs
|
| |
| |
| |
| |
| |
| |
| | |
Now when the dbus connection is dropped, it'll fall back to polling.
I could make it try to reconnect, but there's a FD leak in the dbus
library, so not yet.
|
|/
|
|
|
|
|
|
|
|
|
| |
Hooked up everything that needs to notify on pushes. Note that
syncNewRemote does not notify. This is probably ok, and I'd need to thread
more state through to make it do so.
This is only set up to support a single push notification method; I didn't
use a NotificationBroadcaster. Partly because I don't yet know what info
about pushes needs to be communicated, so my data types are only
preliminary.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This deals with interruptions in network connectevity, by listening
for a new network interface coming up (using dbus to see when
network-manager or wicd do it), and forcing a rescan of
|
| |
|
|
|
|
|
| |
The just created repo has no master branch commits yet. This is now
handled, merging in the master branch from the populated drive.
|
|
|
|
| |
branch yet
|
| |
|
| |
|
|
|
|
| |
remote setup still todo
|
|
|
|
|
|
| |
They're updated to show whether the activity succeeded or failed.
This adds several TODOs to the code to fix later.
|
|
|
|
| |
Makes it easier to edit for consistent voice etc.
|
| |
|
|
|
|
|
| |
Efficiently finding transfers that need to be done to get two repos back
in sync seems like an interesting problem.
|
| |
|
| |
|
|
|
|
|
|
| |
add timestamps to debug messages
Add lots of debug output in the assistant's threads.
|
|
|
|
|
|
|
|
| |
Best dbus events I could find were setupDone from org.kde.Solid.Device.
There may be some spurious events, but that's ok, the code will only
check to see if new mounts are available.
It does not try to auto-start this service if it's not running.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This way, if a mount point was already mounted, but something else
gets mounted there, it'll be seen as a new mount.
|
|
|
|
|
| |
This is an unholy mashup, but it just might work. It works on Linux,
that's all I've tested. :)
|
|
Currently only prints mount points when mounts happen.
|