git-annex/doc/devblog/day_69__catching_up.mdwn
Joey Hess e213ef310f git-annex (5.20140717) unstable; urgency=high
* 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
2014-07-17 11:27:25 -04:00

14 lines
699 B
Markdown

Still working through thanksgiving backlog. Around 55 messages to go.
Wrote hairy code to automatically fix up bad bare repositories created by
recent versions of git-annex. Managed to do it with only 1 stat call
overhead (per local repository). Will probably keep that code in git-annex
for a year or so, despite the bug only being present for a few weeks,
because the repositories that need to be fixed might be on removable drives
that are rarely used.
Various other small bug fixes, including dealing with box.com having
changed their WebDAV endpoint url.
Spent a while evaluating various key/value storage possibilities.
[[bugs/incremental_fsck_should_not_use_sticky_bit]] has the details.