Carlos Martín Nieto 4330ab26b5 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.		2013-04-20 17:54:13 +02:00
..
create.c	branch: Deploy EINVALIDSPEC usage	2012-12-01 08:34:28 +01:00
delete.c	immutable references and a pluggable ref database	2013-03-07 11:01:52 -06:00
foreach.c	Rename ref and reflog apis for consistency	2012-11-27 13:17:45 -08:00
ishead.c	Rename ref and reflog apis for consistency	2012-11-27 13:17:45 -08:00
lookup.c	branch: Deploy EINVALIDSPEC usage	2012-12-01 08:34:28 +01:00
move.c	immutable references and a pluggable ref database	2013-03-07 11:01:52 -06:00
name.c	Added git_branch_name().	2013-01-25 05:24:21 +01:00
remote.c	remote: handle multiple refspecs	2013-04-20 17:54:13 +02:00
upstream.c	branch: add more upstream configuration management	2013-04-11 12:27:25 +02:00
upstreamname.c	branch: rename 'tracking' to 'upstream'	2013-03-30 15:45:57 +01:00