Carlos Martín Nieto 7b5ce2e5c4 clone: don't rely on auto-saving for single-branch ... The code used to rely on the clone code calling the remote's save, which does not happen anymore, meaning that the configuration settings the remote expected were not being written to disk. The run-time configuration was still being affected, so the right branch was being cloned. The tests continued to pass as we did not check for the configuration entires. Fix this by creating the remote with the single-branch refspec we want and checking for its existence in the configuration.		2015-05-17 15:45:37 +02:00
..
clone.c	remote: remove live changing of refspecs	2015-05-13 09:46:36 +02:00
fetch.c	remote: move the tagopt setting to the fetch options	2015-05-13 09:46:36 +02:00
fetchhead.c	remote: move the tagopt setting to the fetch options	2015-05-13 09:46:36 +02:00
push_util.c	push: move main test function to git_remote_push()	2014-11-09 00:01:58 +01:00
push_util.h	remote: move the transport ctor to the callbacks	2015-05-13 09:46:36 +02:00
push.c	remote: remove live changing of refspecs	2015-05-13 09:46:36 +02:00
remotes.c	clone: don't rely on auto-saving for single-branch	2015-05-17 15:45:37 +02:00