- 23 Feb, 2016 1 commit
-
-
Edward Thomson committed
-
- 12 Feb, 2016 1 commit
-
-
Windows defines `timeval` with `long`, which we cannot sanely cope with. Instead, use a custom timeval struct.
Edward Thomson committed
-
- 12 Jan, 2016 1 commit
-
-
Add a new build flag to disable the pool allocator and pass all git_pool_malloc calls straight to git__malloc
Ross Delinger committed
-
- 20 Nov, 2015 1 commit
-
-
Jacques Germishuys committed
-
- 13 Nov, 2015 1 commit
-
-
Vicent Marti committed
-
- 12 Nov, 2015 1 commit
-
-
Carlos Martín Nieto committed
-
- 03 Nov, 2015 2 commits
-
-
When creating a filebuf, detect a directory that exists in our target file location. This prevents a failure later, when we try to move the lock file to the destination.
Edward Thomson committed -
This allows the application to use their own TLS stream, regardless of the capabilities of libgit2 itself.
Carlos Martín Nieto committed
-
- 28 Oct, 2015 2 commits
-
-
Vicent Marti committed
-
Vicent Marti committed
-
- 27 Sep, 2015 1 commit
-
-
Carlos Martín Nieto committed
-
- 19 Sep, 2015 1 commit
-
-
Axel Rasmussen committed
-
- 17 Sep, 2015 4 commits
-
-
`git_futils_mkdir` does not blindly call `git_futils_mkdir_relative`. `git_futils_mkdir_relative` is used when you have some base directory and want to create some path inside of it, potentially removing blocking symlinks and files in the process. This is not suitable for a general recursive mkdir within the filesystem. Instead, when `mkdir` is being recursive, locate the first existent parent directory and use that as the base for `mkdir_relative`.
Edward Thomson committed -
In `mkdir` and `mkdir_r`, ensure that we don't try to remove symlinks that are in our way.
Edward Thomson committed -
Edward Thomson committed
-
Untangle git_futils_mkdir from git_futils_mkdir_ext - the latter assumes that we own everything beneath the base, as if it were being called with a base of the repository or working directory, and is tailored towards checkout and ensuring that there is no bogosity beneath the base that must be cleaned up. This is (at best) slow and (at worst) unsafe in the larger context of a filesystem where we do not own things and cannot do things like unlink symlinks that are in our way.
Edward Thomson committed
-
- 13 Sep, 2015 1 commit
-
-
Ensure that we can iterate the filesystem root and that paths come back well-formed, not with an additional '/'. (eg, when iterating `c:/`, expect that we do not get some path like `c://autoexec.bat`).
Edward Thomson committed
-
- 08 Sep, 2015 2 commits
-
-
Edward Thomson committed
-
Edward Thomson committed
-
- 05 Sep, 2015 1 commit
-
-
We create a lockfile to update files under GIT_DIR. Sometimes these files are actually located elsewhere and a symlink takes their place. In that case we should lock and update the file at its final location rather than overwrite the symlink.
Carlos Martín Nieto committed
-
- 03 Aug, 2015 3 commits
-
-
When an error state is an OOM, make sure that we treat is specially and do not try to free it.
Edward Thomson committed -
Michael Procter committed
-
Michael Procter committed
-
- 24 Jul, 2015 2 commits
-
-
When we have an error renaming the lockfile, we need to make sure that we remove it upon cleanup. For this, we need to keep track of whether we opened the file and whether the rename succeeded. If we did create the lockfile but the rename did not succeed, we remove the lockfile. This won't protect against all errors, but the most common ones (target file is open) does get handled.
Carlos Martín Nieto committed -
When we fail to rename, we currently leave the lockfile laying around. This shows that behaviour.
Carlos Martín Nieto committed
-
- 02 Jul, 2015 1 commit
-
-
Introduce `git__getenv` which is a UTF-8 aware `getenv` everywhere. Make `cl_getenv` use this to keep consistent memory handling around return values (free everywhere, as opposed to only some platforms).
Edward Thomson committed
-
- 24 Jun, 2015 2 commits
-
-
This explains more closely what happens. While here, set an error message.
Carlos Martín Nieto committed -
When we don't own a buffer (asize=0) we currently allow the usage of grow to copy the memory into a buffer we do own. This muddles the meaning of grow, and lets us be a bit cavalier with ownership semantics. Don't allow this any more. Usage of grow should be restricted to buffers which we know own their own memory. If unsure, we must not attempt to modify it.
Carlos Martín Nieto committed
-
- 22 Jun, 2015 1 commit
-
-
Allow files to have mixed line endings instead of skipping processing on them.
Edward Thomson committed
-
- 16 Jun, 2015 1 commit
-
-
Provide functionality to set the time on a filesystem entry, using utimes or futimes on POSIX type systems or SetFileTime on Win32.
Edward Thomson committed
-
- 15 Jun, 2015 1 commit
-
-
Pierre-Olivier Latour committed
-
- 02 Jun, 2015 1 commit
-
-
Pierre-Olivier Latour committed
-
- 29 May, 2015 2 commits
-
-
Edward Thomson committed
-
Treat input bytes as unsigned before doing arithmetic on them, lest we look at some non-ASCII byte (like a UTF-8 character) as a negative value and perform the comparison incorrectly.
Edward Thomson committed
-
- 11 May, 2015 1 commit
-
-
Edward Thomson committed
-
- 01 May, 2015 1 commit
-
-
The _next method shouldn't take a path pointer (and a path_len pointer) as 100% of current users use the full path and ignore the filename. Plus let's add some docs and a unit test.
Edward Thomson committed
-
- 23 Apr, 2015 2 commits
-
-
This is what it's meant all along, but now we actually have multiple implementations, it's clearer to use the name of the library.
Carlos Martín Nieto committed -
As an alternative to OpenSSL when we're on OS X. This one can actually take advantage of stacking the streams.
Carlos Martín Nieto committed
-
- 17 Apr, 2015 1 commit
-
-
Jeff Hostetler committed
-
- 03 Mar, 2015 1 commit
-
-
Jeff Hostetler committed
-