- 08 Jun, 2017 1 commit
-
-
Initially, the setting has been solely used to enable the use of `fsync()` when creating objects. Since then, the use has been extended to also cover references and index files. As the option is not yet part of any release, we can still correct this by renaming the option to something more sensible, indicating not only correlation to objects. This commit renames the option to `GIT_OPT_ENABLE_FSYNC_GITDIR`. We also move the variable from the object to repository source code.
Patrick Steinhardt committed
-
- 02 Mar, 2017 1 commit
-
-
Edward Thomson committed
-
- 01 Mar, 2017 1 commit
-
-
Patrick Steinhardt committed
-
- 28 Feb, 2017 5 commits
-
-
Windows doesn't support it.
Edward Thomson committed -
Rename `GIT_OPT_ENABLE_SYNCHRONIZED_OBJECT_CREATION` -> `GIT_OPT_ENABLE_SYNCHRONOUS_OBJECT_CREATION`.
Edward Thomson committed -
When fsync'ing files, fsync the parent directory in the case where we rename a file into place, or create a new file, to ensure that the directory entry is flushed correctly.
Edward Thomson committed -
Edward Thomson committed
-
Edward Thomson committed
-
- 25 Feb, 2017 2 commits
-
-
Use C style comments as per style guide, and fix mismatching indentation.
Richard Ipsum committed -
This test ensures that it's possible to create a symbolic ref that has arbitrary data as its target. It also ensures it's possible to obtain the target of that symbolic reference from the git_reference object.
Richard Ipsum committed
-
- 11 Apr, 2016 1 commit
-
-
When we turned strict object creation validation on by default, we forgot to inform the refs::create tests of this. They, in fact, believed that strict object creation was off by default. As a result, their cleanup function went and turned strict object creation off for the remaining tests.
Edward Thomson committed
-
- 03 Mar, 2016 1 commit
-
-
Carlos Martín Nieto committed
-
- 28 Feb, 2016 1 commit
-
-
Edward Thomson committed
-
- 12 Nov, 2015 1 commit
-
-
When a (non-empty) directory exists at the reference target location, complain with a more actionable error message.
Edward Thomson committed
-
- 03 Mar, 2015 1 commit
-
-
The signature for the reflog is not something which changes dynamically. Almost all uses will be NULL, since we want for the repository's default identity to be used, making it noise. In order to allow for changing the identity, we instead provide git_repository_set_ident() and git_repository_ident() which allow a user to override the choice of signature.
Carlos Martín Nieto committed
-
- 16 Dec, 2014 1 commit
-
-
Validate loose reference names on Win32.
Edward Thomson committed
-
- 01 Jul, 2014 1 commit
-
-
Edward Thomson committed
-
- 15 Jan, 2014 1 commit
-
-
Any well-behaved program should write a descriptive message to the reflog whenever it updates a reference. Let's make this more prominent by removing the version without the reflog parameters.
Carlos Martín Nieto committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 07 Mar, 2013 1 commit
-
-
Edward Thomson committed
-
- 01 Dec, 2012 2 commits
- 27 Nov, 2012 1 commit
-
-
Ben Straub committed
-
- 30 Sep, 2012 1 commit
-
-
Indicate whether the error comes from the ref already existing or elsewhere. We always perform the check and this lets the user write more concise code.
Carlos Martín Nieto committed
-
- 25 Sep, 2012 1 commit
-
-
nulltoken committed
-
- 17 Jul, 2012 1 commit
-
-
Ben Straub committed
-
- 02 May, 2012 1 commit
-
-
Vicent Martí committed
-
- 03 Apr, 2012 1 commit
-
-
Vicent Martí committed
-
- 01 Apr, 2012 1 commit
-
-
Ben Straub committed
-
- 30 Mar, 2012 1 commit
-
-
Ben Straub committed
-