Carlos Martín Nieto 46c8f7f845 remote: accept a repo and name for renaming ... Remote objects are not meant to be changed from under the user. We did this in rename, but only the name and left the refspecs, such that a save would save the wrong refspecs (and a fetch and anything else would use the wrong refspecs). Instead, let's simply take a name and not change any loaded remote from under the user.		2014-10-24 16:25:59 +02:00
..
createthenload.c	Rename tests-clar to tests	2013-11-14 14:05:52 -08: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	remote: implement opportunistic remote-tracking branch updates	2014-09-30 15:43:24 +02:00
remotes.c	Clean up some leaks in the test suite	2014-09-17 03:19:40 +02:00
rename.c	remote: accept a repo and name for renaming	2014-10-24 16:25:59 +02:00