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
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
I've been out sick. However, some things kept happening. Mesar contributed
|
|
a build host, and the linux and android builds are now happening, hourly,
|
|
there. (Thanks as well to the two other people who also offered hostng.)
|
|
And I made a minor release to fix a bug in the test suite that I was pleased
|
|
three different people reported.
|
|
|
|
Today, my main work was getting git-annex to notice when a gcrypt remote
|
|
located on some removable drive mount point is not the same gcrypt remote
|
|
that was mounted there before. I was able to finesse this so it
|
|
re-configures things to use the new gcrypt remote, as long as it's a
|
|
special remote it knows about. (Otherwise it has to ignore the remote.)
|
|
So, encrypted repos on removable drives will work just as well as
|
|
non-encrypted repos!
|
|
|
|
Also spent a while with rsync.net tech support trying to work out why
|
|
someone's git-annex apparently opened a lot of concurrent ssh connections
|
|
to rsync.net. Have not been able to reproduce the problem though.
|
|
|
|
Also, a lot of catch-up to traffic. Still 63 messages backlogged however,
|
|
and still not entirely well..
|