git-annex/doc/devblog/day_184__windows_month.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

22 lines
1.1 KiB
Markdown

It's officially a Windows porting month. Now that I'm half way through it
and with the last week of the month going to be a vacation, this makes
sense.
Today, finished up dealing with the timezone/timestamp issues on Windows.
This got stranger and stranger the closer I looked at it. After a timestamp
change, a program that was already running will see one timestamp, while a
program that is started after the change will see another one! My approach
works pretty much no matter how Windows goes insane though, and always
recovers a true timestamp. Yay.
Also fixed a regression test failure on Windows, which turned out to be
rooted in a bug in the command queue runner, which neglected to pass
along environment overrides on Windows.
Then I spent 5 hours tracking down a tricky
test suite failure on Windows, which turned out to also
affect FAT and be a recent reversion that has as it's
root cause a [fun bug in git itself](http://marc.info/?l=git&m=140262402204212&w=2).
Put in a not very good workaround. Thank goodness for test suites!
Also got the arm autobuilder unstuck. Release tomorrow.