- 20 Apr, 2013 2 commits
-
-
Introduce git_remote_{fetch,push}_refspecs() to get a list of refspecs from the remote and rename the refspec-adding functions to a less silly name. Use this instead of the vector index hacks in the tests.
Carlos Martín Nieto committed -
A remote can have a multitude of refspecs. Up to now our git_remote's have supported a single one for each fetch and push out of simplicity to get something working. Let the remotes and internal code know about multiple remotes and get the tests passing with them. Instead of setting a refspec, the external users can clear all and add refspecs. This should be enough for most uses, though we're still missing a querying function.
Carlos Martín Nieto committed
-
- 19 Apr, 2013 1 commit
-
-
Edward Thomson 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
-
- 11 Apr, 2013 1 commit
-
-
Add functions to set and unset the upstream configuration to complement the getter we already have.
Carlos Martín Nieto committed
-
- 09 Apr, 2013 1 commit
-
-
Ben Straub committed
-
- 08 Apr, 2013 1 commit
-
-
Ben Straub committed
-
- 07 Apr, 2013 2 commits
-
-
Vicent Marti committed
-
Signed-off-by: Greg Price <price@mit.edu>
Greg Price committed
-
- 31 Mar, 2013 2 commits
-
-
nulltoken committed
-
Return the size we'd need to write to instead of simply an error. Split the function into two to be used later by the upstream configuration functions.
Carlos Martín Nieto 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
-
- 14 Mar, 2013 1 commit
-
-
This fixes various build warnings on Mac and Windows (64-bit).
Russell Belfer committed
-
- 07 Mar, 2013 2 commits
-
-
Edward Thomson committed
-
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
-
- 26 Feb, 2013 1 commit
-
-
The new tests were not taking core.filemode into account when testing file modes after repo initialization. Fixed that and some other Windows warnings that have crept in.
Russell Belfer committed
-
- 22 Feb, 2013 2 commits
- 11 Feb, 2013 3 commits
-
-
Fix libgit2/libgit2sharp#318
nulltoken committed -
nulltoken committed
-
Jameson Miller committed
-
- 08 Feb, 2013 1 commit
-
-
Scott J. Goldman committed
-
- 05 Feb, 2013 1 commit
-
-
Fix #1308
nulltoken committed
-
- 03 Feb, 2013 2 commits
- 31 Jan, 2013 1 commit
-
-
A leading slash confuses the name normalization code when the flags include ALLOW_ONELEVEL. Catch this case in particular to avoid triggering an assertion in the uppercase check which expects us not to pass it an empty string. The existing tests don't catch this as they simply use the NORMAL flag. This fixes #1300.
Carlos Martín Nieto committed
-
- 25 Jan, 2013 2 commits
-
-
Replaced all cl_assert(!strcmp()) or semantically equivalent forms by cl_assert_equal_s().
Sebastian Bauer committed -
This is a convenience function to get the branch name of a given ref. The returned branch name is compatible with the name that can be supplied e.g. to git_branch_lookup(). That is, the prefixes "refs/heads" or "refs/remotes" are omitted. Also added a new test for testing the new function.
Sebastian Bauer committed
-
- 23 Jan, 2013 1 commit
-
-
as per @vmg's request
Scott J. Goldman committed
-
- 16 Jan, 2013 1 commit
-
-
nulltoken committed
-
- 04 Jan, 2013 1 commit
-
-
Add the jGit license block to tests derrived from jGit as per the terms of the BSD license.
Martin Woodward committed
-
- 10 Dec, 2012 1 commit
-
-
Ben Straub committed
-
- 01 Dec, 2012 5 commits