summaryrefslogtreecommitdiff
path: root/tests-clar/online/fetchhead.c
diff options
context:
space:
mode:
authorCarlos Martín Nieto <cmn@dwim.me>2013-04-20 04:43:28 +0200
committerCarlos Martín Nieto <cmn@dwim.me>2013-04-20 17:54:13 +0200
commit4330ab26b53c0e1bf8cbb5e65704f65e3d116eba (patch)
tree14bf8d854854298bfe43b3a02c8c26f59377c988 /tests-clar/online/fetchhead.c
parente5a27f039ee3ae1291fd5084707c3f9c168f10ba (diff)
downloadlibgit2-4330ab26b53c0e1bf8cbb5e65704f65e3d116eba.tar.gz
remote: handle multiple refspecs
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.
Diffstat (limited to 'tests-clar/online/fetchhead.c')
-rw-r--r--tests-clar/online/fetchhead.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/tests-clar/online/fetchhead.c b/tests-clar/online/fetchhead.c
index a8a5bb918..3cbdc7e93 100644
--- a/tests-clar/online/fetchhead.c
+++ b/tests-clar/online/fetchhead.c
@@ -42,8 +42,10 @@ static void fetchhead_test_fetch(const char *fetchspec, const char *expected_fet
cl_git_pass(git_remote_load(&remote, g_repo, "origin"));
git_remote_set_autotag(remote, GIT_REMOTE_DOWNLOAD_TAGS_AUTO);
- if(fetchspec != NULL)
- git_remote_set_fetchspec(remote, fetchspec);
+ if(fetchspec != NULL) {
+ git_remote_clear_refspecs(remote);
+ git_remote_add_fetchspec(remote, fetchspec);
+ }
cl_git_pass(git_remote_connect(remote, GIT_DIRECTION_FETCH));
cl_git_pass(git_remote_download(remote, NULL, NULL));