1. 04 Apr, 2016 1 commit
  2. 30 Mar, 2016 2 commits
  3. 19 Feb, 2016 2 commits
  4. 18 Feb, 2016 1 commit
  5. 17 Feb, 2016 3 commits
  6. 16 Feb, 2016 2 commits
  7. 12 Feb, 2016 1 commit
  8. 09 Feb, 2016 2 commits
  9. 06 Feb, 2016 2 commits
  10. 03 Feb, 2016 1 commit
  11. 02 Feb, 2016 6 commits
  12. 21 Jan, 2016 2 commits
  13. 14 Jan, 2016 8 commits
  14. 10 Jan, 2016 2 commits
  15. 09 Jan, 2016 1 commit
    • Jakob Unterwurzacher's avatar
      Fix several Utimens-related build problems on OSX · 07d43e8a
      Jakob Unterwurzacher authored
      Properly implementing Utimens caused the OSX build to break because
      the utimensat system call is not available there.
      
      This patch reverts the OSX implementation of Utimens to using
      syscall.Utimes(). This is not actually correct but the best we can do.
      
      Thanks to @spaghetti2514 who reported the issue and tested the patches.
      07d43e8a
  16. 17 Dec, 2015 2 commits
  17. 15 Dec, 2015 2 commits
    • Eliot Courtney's avatar
      148d3830
    • Jakob Unterwurzacher's avatar
      loopback: fix Utimens on symlinks · d36ee9dd
      Jakob Unterwurzacher authored
      The problem was that os.Chtimes() operates on the target of the
      symlink and not on the symlink itself.
      When tar extracts an archive containing a symlink, it actually wants
      to set the times on the symlink. This can also be tested using
      "touch -h".
      
      This patch adds a wrapper for the Linux utimensat(2) syscall
      that allows passing flags along with a unit test.
      
      It uses the flag AT_SYMLINK_NOFOLLOW to implement
      loopbackFileSystem.Utimens() properly.
      
      It also add handling for UTIME_NOW and UTIME_OMIT that was already
      present in loopbackFile.Utimens() but missing in loopbackFileSystem.
      
      Fixes issue 81 ( https://github.com/hanwen/go-fuse/issues/81 ).
      d36ee9dd