diff options
author | Joey Hess <joey@kitenet.net> | 2013-09-24 17:28:21 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-09-24 17:28:21 -0400 |
commit | 8f802e4b57f43a46199424c13ef28d114d49792c (patch) | |
tree | 45d5ee58831417bd2ab42b9d3b39d601efc1d902 /doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn | |
parent | e06bf0da75294b33188cde319c29d93266fd4bb3 (diff) |
devblog
Diffstat (limited to 'doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn')
-rw-r--r-- | doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn b/doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn new file mode 100644 index 000000000..0e4142b7c --- /dev/null +++ b/doc/devblog/day_20__gcrypt_and_git-annex-shell.mdwn @@ -0,0 +1,14 @@ +Added support for gcrypt remotes to git-annex-shell. Now gcrypt special +remotes probe when they are set up to see if the remote system has a +suitable git-annex-shell, and if so all commands are sent to it. Kept the +direct rsync mode working as a fallback. + +It turns out I made a bad decision when first adding gcrypt support to +git-annex. To make implementation marginally easier, I decided to not +put objects inside the usual `annex/objects` directory in a gcrypt remote. +But that lack of consistency would have made adding support to +git-annex-shell a lot harder. So, I decided to change this. Which +means that anyone already using gcrypt with git-annex will need to +[[manually_move_files_around|upgrades/gcrypt]]. + +Today's work was sponsored by Tobias Nix. |