b6d46c212e
* unannex, uninit: Avoid committing after every file is unannexed,
for massive speedup.
* --notify-finish switch will cause desktop notifications after each
file upload/download/drop completes
(using the dbus Desktop Notifications Specification)
* --notify-start switch will show desktop notifications when each
file upload/download starts.
* webapp: Automatically install Nautilus integration scripts
to get and drop files.
* tahoe: Pass -d parameter before subcommand; putting it after
the subcommand no longer works with tahoe-lafs version 1.10.
(Thanks, Alberto Berti)
* forget --drop-dead: Avoid removing the dead remote from the trust.log,
so that if git remotes for it still exist anywhere, git annex info
will still know it's dead and not show it.
* git-annex-shell: Make configlist automatically initialize
a remote git repository, as long as a git-annex branch has
been pushed to it, to simplify setup of remote git repositories,
including via gitolite.
* add --include-dotfiles: New option, perhaps useful for backups.
* Version 5.20140227 broke creation of glacier repositories,
not including the datacenter and vault in their configuration.
This bug is fixed, but glacier repositories set up with the broken
version of git-annex need to have the datacenter and vault set
in order to be usable. This can be done using git annex enableremote
to add the missing settings. For details, see
http://git-annex.branchable.com/bugs/problems_with_glacier/
* Added required content configuration.
* assistant: Improve ssh authorized keys line generated in local pairing
or for a remote ssh server to set environment variables in an
alternative way that works with the non-POSIX fish shell, as well
as POSIX shells.
# imported from the archive
34 lines
1.8 KiB
Markdown
34 lines
1.8 KiB
Markdown
Got the assistant to check again, just before starting a transfer, if
|
|
the remote still wants the object. This should be all that's needed to
|
|
handle the case where there is a transfer remote on the internet somewhere,
|
|
and a locally paired client on the LAN. As long as the paired repository
|
|
has a lower cost value, it will be sent any new file first, and if that
|
|
is the only client, the file will not be sent to the transfer remote at
|
|
all.
|
|
|
|
But.. locally paired repos did not have a lower cost set, at all.
|
|
So I made their cost be set to 175 when they're created. Anyone
|
|
who already did local pairing should make sure the Repositories
|
|
list shows locally paired repositories above transfer remotes.
|
|
|
|
Which brought me to needing an easy way to reorder that list of remotes,
|
|
which I plan to do by letting the user drag and drop remotes around,
|
|
which will change their cost accordingly. Implementing that has two
|
|
pain points:
|
|
|
|
1. Often a lot of remotes will have the same default cost value.
|
|
So how to insert a remote in between two that have cost 100?
|
|
This would be easy if git-annex didn't have these cost numbers,
|
|
and instead just had an ordered list of remotes.. but it doesn't.
|
|
Instead, dragging remotes in the list will sometimes need to change
|
|
the costs of others, to make room to insert them in. It's BASIC
|
|
renumbering all over again. So I wrote some code to do this with as
|
|
little bother as possible.
|
|
|
|
2. Drag and drop means javascript. I got the basics going quickly with
|
|
jquery-ui, only to get stuck for over an hour on some CSS issue
|
|
that made lines from the list display all weird while being dragged.
|
|
It is always something like this with javascript..
|
|
|
|
So I've got these 2 peices working, and even have the AJAX call
|
|
firing, but it's not quite wired up just yet. Tomorrow.
|