- 11 Apr, 2016 1 commit
-
-
If we cannot dwim the input, set the error message to be explicit about that. Otherwise we leave the error for the last failed lookup, which can be rather unexpected as it mentions a remote when the user thought they were trying to look up a branch.
Carlos Martín Nieto committed
-
- 01 Jul, 2014 1 commit
-
-
Edward Thomson committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 11 Oct, 2013 1 commit
-
-
This lets the reference code return not-found when the user asks to look up a reference when in fact they pass a namespace.
Carlos Martín Nieto committed
-
- 07 Mar, 2013 1 commit
-
-
It's somewhat common to try to write "/refs/tags/something". There is no easy way to catch it during the main body of the function, as there is no way to distinguish whether it's a leading slash or a double slash somewhere in the middle. Catch this at the beginning so we don't trigger the assert in is_all_caps_and_underscore().
Carlos Martín Nieto committed
-
- 27 Nov, 2012 1 commit
-
-
Ben Straub committed
-
- 25 Sep, 2012 1 commit
-
-
nulltoken committed
-
- 23 Apr, 2012 1 commit
-
-
Russell Belfer committed
-
- 17 Apr, 2012 1 commit
-
-
Adds a new public reference function `git_reference_lookup_oid` that directly resolved a reference name to an OID without returning the intermediate `git_reference` object (hence, no free needed). Internally, this adds a `git_reference_lookup_resolved` function that combines looking up and resolving a reference. This allows us to be more efficient with memory reallocation. The existing `git_reference_lookup` and `git_reference_resolve` are reimplmented on top of the new utility and a few places in the code are changed to use one of the two new functions.
Russell Belfer committed
-