- 19 Apr, 2016 1 commit
-
-
Carlos Martín Nieto committed
-
- 08 Sep, 2015 1 commit
-
-
Matt Burke committed
-
- 13 May, 2015 3 commits
-
-
This is another option which we should not be keeping in the remote, but is specific to each particular operation.
Carlos Martín Nieto committed -
While this will rarely be different from the default, having it in the remote adds yet another setting it has to keep around and can affect its behaviour. Move it to the options.
Carlos Martín Nieto committed -
Having the setting be different from calling its actions was not a great idea and made for the sake of the wrong convenience. Instead of that, accept either fetch options, push options or the callbacks when dealing with the remote. The fetch options are currently only the callbacks, but more options will be moved from setters and getters on the remote to the options. This does mean passing the same struct along the different functions but the typical use-case will only call git_remote_fetch() or git_remote_push() and so won't notice much difference.
Carlos Martín Nieto committed
-
- 13 Mar, 2015 1 commit
-
-
This was but down to 5 when GitHub made a change to their server which made them stop honouring the include-tag request. This has recently been corrected, so we can bring it back up to six.
Carlos Martín Nieto 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
-
- 19 Nov, 2014 1 commit
-
-
When we fetch twice with the same remote object, we did not properly clear the connection flags, so we would leak state from the last connection. This can cause the second fetch with the same remote object to fail if using a HTTP URL where the server redirects to HTTPS, as the second fetch would see `use_ssl` set and think the initial connection wanted to downgrade the connection.
Carlos Martín Nieto committed
-
- 08 Nov, 2014 1 commit
-
-
This brings it in line with the rest of the lookup functions.
Carlos Martín Nieto committed
-
- 30 Sep, 2014 1 commit
-
-
With opportunistic ref updates, git has introduced the concept of having base refspecs *and* refspecs that are active for a particular fetch. Let's start by letting the user override the refspecs for download.
Carlos Martín Nieto committed
-
- 21 May, 2014 1 commit
-
-
Add a symref_target field to git_remote_head to expose the symref mappings to the user.
Carlos Martín Nieto committed
-
- 03 Mar, 2014 1 commit
-
-
Matthias Bartelmeß committed
-
- 05 Feb, 2014 1 commit
-
-
Also added a test for git_remote_fetch.
Ben Straub committed
-
- 31 Dec, 2013 1 commit
-
-
I am not sure why there was 6 in the first place.
Marek Šuppa committed
-
- 11 Dec, 2013 1 commit
-
-
This changes the behavior of callbacks so that the callback error code is not converted into GIT_EUSER and instead we propagate the return value through to the caller. Instead of using the giterr_capture and giterr_restore functions, we now rely on all functions to pass back the return value from a callback. To avoid having a return value with no error message, the user can call the public giterr_set_str or some such function to set an error message. There is a new helper 'giterr_set_callback' that functions can invoke after making a callback which ensures that some error message was set in case the callback did not set one. In places where the sign of the callback return value is meaningful (e.g. positive to skip, negative to abort), only the negative values are returned back to the caller, obviously, since the other values allow for continuing the loop. The hardest parts of this were in the checkout code where positive return values were overloaded as meaningful values for checkout. I fixed this by adding an output parameter to many of the internal checkout functions and removing the overload. This added some code, but it is probably a better implementation. There is some funkiness in the network code where user provided callbacks could be returning a positive or a negative value and we want to rely on that to cancel the loop. There are still a couple places where an user error might get turned into GIT_EUSER there, I think, though none exercised by the tests.
Russell Belfer committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 11 Nov, 2013 1 commit
-
-
The callback-based method of listing remote references dates back to the beginning of the network code's lifetime, when we didn't know any better. We need to keep the list around for update_tips() after disconnect() so let's make use of this to simply give the user a pointer to the array so they can write straightforward code instead of having to go through a callback.
Carlos Martín Nieto committed
-
- 08 Nov, 2013 1 commit
-
-
Victor Garcia committed
-
- 07 Nov, 2013 1 commit
-
-
Victor Garcia committed
-
- 02 Oct, 2013 1 commit
-
-
The text progress and update_tips callbacks are already part of the struct, which was meant to unify the callback setup, but the download one was left out.
Carlos Martín Nieto committed
-
- 24 Sep, 2013 1 commit
-
-
The subtransport path was relying on pointing to data owned by the remote which meant that after a redirect, the updated path was getting lost for future requests. This updates the http transport to strdup the path and maintain its own lifetime. This also pulls responsibility for parsing the URL back into the http transport and isolates the functions that parse and free that connection data so that they can be reused between the initial parsing and the redirect parsing.
Russell Belfer committed
-
- 15 Apr, 2013 1 commit
-
-
Keep the data around until free, as expected by our own fetch example
Carlos Martín Nieto committed
-
- 05 Feb, 2013 2 commits
-
-
Ben Straub committed
-
This works by having the indexer watch the return code of the callback, so will only take effect on object boundaries.
Ben Straub committed
-
- 02 Jan, 2013 2 commits
-
-
Vicent Marti committed
-
Vicent Marti committed
-
- 20 Dec, 2012 2 commits
-
-
git_remote_add -> git_remote_create git_remote_new -> git_remote_create_inmemory
Ben Straub committed -
Ben Straub committed
-
- 14 Dec, 2012 2 commits
-
-
Ben Straub committed
-
Ben Straub committed
-
- 13 Dec, 2012 2 commits
-
-
Ben Straub committed
-
Ben Straub committed
-
- 05 Dec, 2012 1 commit
-
-
Vicent Marti committed
-
- 01 Dec, 2012 1 commit
-
-
nulltoken committed
-
- 30 Nov, 2012 2 commits
-
-
Ben Straub committed
-
Ben Straub committed
-
- 28 Nov, 2012 3 commits
-
-
nulltoken committed
-
nulltoken committed
-
Philip Kelley committed
-
- 27 Nov, 2012 1 commit
-
-
Includes typedef for git_direction, and renames for GIT_DIR_[FETCH|PUSH] to GIT_DIRECTION_(\1).
Ben Straub committed
-