| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Not yet used by git-annex, but this will allow faster transfers etc than
using individual ssh connections and rsync.
Not called git-annex-shell p2p, because git-annex p2p does something
else and I don't want two subcommands with the same name between the two
for sanity reasons.
This commit was sponsored by Øyvind Andersen Holm.
|
| | |
|
| | |
|
| |
|
|
| |
sorry for the noise again...
|
| | |
|
| |
|
|
|
|
| |
The direct flag is also set when sending unlocked content, to support old
versions of git-annex-shell. At some point, the direct flag will be
removed, and only the unlocked flag will be used.
|
| |
|
|
| |
content.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now it suffices to run git remote add, followed by git-annex sync. Now the
remote is automatically initialized for use by git-annex, where before the
git-annex branch had to manually be pushed before using git-annex sync.
Note that this involved changes to git-annex-shell, so if the remote is
using an old version, the manual push is still needed.
Implementation required git-annex-shell be changed, so configlist can
autoinit a repository even when no git-annex branch has been pushed yet.
Unfortunate because we'll have to wait for it to get deployed to servers
before being able to rely on this change in the documentation.
Did consider making git-annex sync push the git-annex branch to repos that
didn't have a uuid, but this seemed difficult to do without complicating it
in messy ways.
It would be cleaner to split a command out from configlist to handle
the initialization. But this is difficult without sacrificing backwards
compatability, for users of old git-annex versions which would not use the
new command.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
One of my
for f in `ls *.mdwn | sort -R`; do aspell -c $f; sleep 2; done
sessions.
3647f704-e510-11e4-bf50-000df06acc56
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This will be used by the remote-daemon to quickly tell when changes have
been pushed from some other repository into a ssh remote.
Adjusted the remote-daemon protocol to communicate changed shas, rather
than git branch refs. This way, it can easily check if a sha is new.
This commit was sponsored by Carlos Trijueque Albarran.
|
| |
|
|
| |
repository, as long as a git-annex branch has been pushed to it, to simplify setup of remote git repositories, including via gitolite.
|
| |
|
|
|
| |
This was the least-bad alternative to get dedicated key gcrypt repos
working in the assistant.
|
| |
|
|
|
| |
Checks the key's size and checksum. This is sorta expensive, but it avoids
needing to add another round-trip to the protocol.
|
| |
|
|
| |
operating on a specified directory.
|
| |
|
|
| |
Finally done with progressbars!
|
| |
|
|
|
| |
TODO: Use this when running sendkey, to feed back transfer info from the
client side rsync.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Eventually, git-annex might try running this after making changes to
a remote. I have not yet thought of a good way for it to tell which
remotes it needs to run it on though. It can't just do it when
shutting down a cached ssh connection, because ssh connection caching
is optional, and that would not handle local remotes not accessed over ssh
either.
|
| | |
|
| |
|
|
|
|
| |
environment variables can be set to limit what commands can be run.
This could be used by eg, gitolite.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
This is not yet complete, as it does not allow starting rsync or scp.
|
Joey Hess
edward
Antoine Beaupré
anarcat
Øyvind A. Holm
Joey Hess