Pierre-Olivier Latour d3cd7da51f Fixed active_refspecs field not initialized on new git_remote objects ... When creating a new remote, contrary to loading one from disk, active_refspecs was not populated. This means that if using the new remote to push, git_push_update_tips() will be a no-op since it checks the refspecs passed during the push against the base ones i.e. active_refspecs. And therefore the local refs won't be created or updated after the push operation.		2014-11-17 22:46:22 +09:00
..
createthenload.c	remote: rename _load() to _lookup()	2014-11-08 13:28:27 +01:00
defaultbranch.c	clone: correct handling of an unborn HEAD	2014-09-02 13:10:19 +02:00
delete.c	remote: accept a repository and remote name for deletion	2014-09-30 16:09:55 +02:00
isvalidname.c	Rename tests-clar to tests	2013-11-14 14:05:52 -08:00
local.c	Fixed active_refspecs field not initialized on new git_remote objects	2014-11-17 22:46:22 +09:00
remotes.c	Merge pull request #2698 from libgit2/cmn/fetchhead-refactor	2014-11-08 17:05:13 -05:00
rename.c	remote: rename _load() to _lookup()	2014-11-08 13:28:27 +01:00