1. 07 Nov, 2011 1 commit
  2. 29 Oct, 2011 1 commit
  3. 27 Oct, 2011 1 commit
    • windows: Add support for non-UTF codepages · 11d51ca6
      Our previous assumption that all paths in Windows are encoded in UTF-8
      is rather weak, specially when considering that Git is
      encoding-agnostic.
      
      These set of functions allow the user to change the library's active
      codepage globally, so it is possible to access paths and files on all
      international versions of Windows.
      
      Note that the default encoding here is UTF-8 because we assume that 99%
      of all Git repositories will be in UTF-8.
      
      Also, if you use non-ascii characters in paths, anywhere, please burn on
      a fire.
      Vicent Marti committed
  4. 14 Oct, 2011 1 commit
  5. 09 Oct, 2011 1 commit
  6. 05 Oct, 2011 1 commit
  7. 29 Sep, 2011 2 commits
  8. 28 Sep, 2011 1 commit
  9. 27 Sep, 2011 1 commit
  10. 22 Sep, 2011 1 commit
  11. 21 Sep, 2011 2 commits
  12. 19 Sep, 2011 4 commits
  13. 18 Sep, 2011 1 commit
    • Cleanup legal data · bb742ede
      1. The license header is technically not valid if it doesn't have a
      copyright signature.
      
      2. The COPYING file has been updated with the different licenses used in
      the project.
      
      3. The full GPLv2 header in each file annoys me.
      Vicent Marti committed
  14. 31 Aug, 2011 1 commit
  15. 30 Aug, 2011 2 commits
  16. 18 Aug, 2011 1 commit
  17. 09 Jul, 2011 2 commits
    • posix: Portable `vsnprintf` · 2fc78e70
      Our good, lovely folks at Microsoft decided that there was no good
      reason to make `vsnprintf` compilant with the C standard, so that
      function in Windows returns -1 on overflow, instead of returning the
      actual byte count needed to write the full string.
      
      We now handle this situation more gracefully with the POSIX
      compatibility layer, by returning the needed byte size using an
      auxiliary method instead of blindly resizing the target buffer until it
      fits.
      
      This means we can now support `printf`s of any size by allocating a
      temporary buffer. That's good.
      Vicent Marti committed
  18. 05 Jul, 2011 5 commits
  19. 03 Jul, 2011 1 commit
  20. 23 May, 2011 2 commits
  21. 08 May, 2011 1 commit
  22. 20 Mar, 2011 1 commit
  23. 15 Mar, 2011 1 commit
  24. 11 Jan, 2011 1 commit
  25. 20 Jan, 2010 2 commits
  26. 15 Jun, 2009 1 commit
    • win32: Add an fsync() implementation for windows · c79dded3
      For information on FlushFileBuffers(), see the msdn document
      at msdn.microsoft.com/en-us/library/aa364439(VS.85).aspx
      
      Note that Windows 2000 is shown as the minimum windows version
      to support FlushFileBuffers(), so if we wish to support Win9X
      and NT4, we will need to add code to dynamically check if
      kernel32.dll contains the function.
      
      The only error return mentioned in the msdn document is
      ERROR_INVALID_HANDLE, which is returned if the file/device
      (eg console) is not buffered. The fsync(2) manpage says that
      EINVAL is returned in errno, if "fd is bound to a special
      file which does not support synchronization".
      
      Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
      Ramsay Jones committed
  27. 05 Jun, 2009 1 commit