- 03 Jul, 2017 1 commit
-
-
Next to including several files, our "common.h" header also declares various macros which are then used throughout the project. As such, we have to make sure to always include this file first in all implementation files. Otherwise, we might encounter problems or even silent behavioural differences due to macros or defines not being defined as they should be. So in fact, our header and implementation files should make sure to always include "common.h" first. This commit does so by establishing a common include pattern. Header files inside of "src" will now always include "common.h" as its first other file, separated by a newline from all the other includes to make it stand out as special. There are two cases for the implementation files. If they do have a matching header file, they will always include this one first, leading to "common.h" being transitively included as first file. If they do not have a matching header file, they instead include "common.h" as first file themselves. This fixes the outlined problems and will become our standard practice for header and source files inside of the "src/" from now on.
Patrick Steinhardt committed
-
- 05 May, 2017 1 commit
-
-
Support '..' and '...' ranges where one side is not specified. The unspecified side defaults to HEAD. Closes #4223
William Bain committed
-
- 29 Dec, 2016 1 commit
-
-
Error messages should be sentence fragments, and therefore: 1. Should not begin with a capital letter, 2. Should not conclude with punctuation, and 3. Should not end a sentence and begin a new one
Edward Thomson committed
-
- 06 Oct, 2016 1 commit
-
-
Arthur Schreiber committed
-
- 05 Sep, 2014 1 commit
-
-
Vicent Marti committed
-
- 05 Feb, 2014 1 commit
-
-
Now that we no longer fail to push non-commits on a glob, let's search on all refs when we rev-parse syntax asks us to match text.
Carlos Martín Nieto committed
-
- 20 Jan, 2014 1 commit
-
-
Linquize committed
-
- 02 Oct, 2013 1 commit
-
-
References and their logs are logically coupled, let's make it so in the code by moving the fs-based reflog implementation to live next to the fs-based refs one. As part of the change, make the function take names rather than references, as only the names are relevant when looking up and handling reflogs.
Carlos Martín Nieto committed
-
- 11 Sep, 2013 1 commit
-
-
nulltoken committed
-
- 07 Sep, 2013 2 commits
- 19 Aug, 2013 1 commit
-
-
Carlos Martín Nieto committed
-
- 15 Aug, 2013 2 commits
-
-
Evan Hanson committed
-
This fixes a small memory leak in git_revparse where early returns on errors from git_revparse_single cause a free() on the (reallocated) left side of the revspec to be skipped.
Evan Hanson committed
-
- 13 Jul, 2013 1 commit
-
-
Fix #1722
nulltoken committed
-
- 12 Jun, 2013 1 commit
-
-
This fixes problems with missing function prototypes and 64-bit data issues on Windows.
Russell Belfer committed
-
- 16 May, 2013 3 commits
- 15 May, 2013 1 commit
-
-
nulltoken committed
-
- 07 May, 2013 1 commit
-
-
Extract this function out of the rev-parse code to be able to DWIM a reference instead of its target.
Carlos Martín Nieto committed
-
- 01 May, 2013 1 commit
-
-
There are many paths through revparse that may return an error code without reporting an error, I believe. This fixes one of them. Because of the backtracking in revparse, it is pretty complicated to fix the others.
Russell Belfer committed
-
- 18 Apr, 2013 1 commit
-
-
Russell Belfer committed
-
- 15 Apr, 2013 4 commits
-
-
Vicent Marti committed
-
Vicent Marti committed
-
This will probably prevent many lookup/free operations in calling code.
Ben Straub committed -
Ben Straub committed
-
- 10 Apr, 2013 1 commit
-
-
Vicent Marti committed
-
- 09 Apr, 2013 1 commit
-
-
Ben Straub committed
-
- 08 Apr, 2013 1 commit
-
-
Ben Straub committed
-
- 07 Apr, 2013 1 commit
-
-
Signed-off-by: Greg Price <price@mit.edu>
Greg Price committed
-
- 30 Mar, 2013 1 commit
-
-
The term 'tracking' is overloaded. Help distinguish what we mean by using 'upstream' for this part of the library.
Carlos Martín Nieto committed
-
- 17 Mar, 2013 1 commit
-
-
Implicit type conversion argument of function to size_t type Suspicious sequence of types castings: size_t -> int -> size_t Consider reviewing the expression of the 'A = B == C' kind. The expression is calculated as following: 'A = (B == C)' Unsigned type is never < 0
Arkadiy Shapkin committed
-
- 07 Mar, 2013 1 commit
-
-
Edward Thomson committed
-
- 03 Feb, 2013 2 commits
- 08 Jan, 2013 1 commit
-
-
Edward Thomson committed
-
- 01 Dec, 2012 1 commit
-
-
nulltoken committed
-
- 27 Nov, 2012 2 commits
-
-
Russell Belfer committed
-
Ben Straub committed
-