e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
14 lines
761 B
Markdown
14 lines
761 B
Markdown
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.
|