Carlos Martín Nieto 5014fe95f5 branch: error out if we cannot find the remote ... When we look for which remote corresponds to a remote-tracking branch, we look in the refspecs to see which ones matches. If none do, we should abort. We currently ignore the error message from this operation, so let's not do that anymore. As part of the test we're writing, let's test for the expected behaviour if we cannot find a refspec which tells us what the remote-tracking branch for a remote would look like.		2015-05-22 12:31:39 +02:00
..
create.c	Add tests for the annotated versions of ref-modifying functions	2015-03-16 16:57:30 +01:00
delete.c	repository: remove log message override for switching the active branch	2015-03-03 14:40:50 +01:00
ishead.c	Remove the signature from ref-modifying functions	2015-03-03 14:40:50 +01:00
iterator.c	Remove the signature from ref-modifying functions	2015-03-03 14:40:50 +01:00
lookup.c	Rename tests-clar to tests	2013-11-14 14:05:52 -08:00
move.c	refdb: use the same id for old and new when renaming a reference	2015-03-08 16:50:27 +01:00
name.c	Rename tests-clar to tests	2013-11-14 14:05:52 -08:00
remote.c	remote: remove live changing of refspecs	2015-05-13 09:46:36 +02:00
upstream.c	branch: error out if we cannot find the remote	2015-05-22 12:31:39 +02:00
upstreamname.c	branch: move to git_buf when outputting newly-allocated strings	2014-01-27 04:44:05 +01:00