Merge branch 'js/remote-rename-with-half-configured-remote'
commitfe575f06532bde1e672a2313fd76ef09b66fc355
authorJunio C Hamano <gitster@pobox.com>
Tue, 31 Jan 2017 21:14:59 +0000 (31 13:14 -0800)
committerJunio C Hamano <gitster@pobox.com>
Tue, 31 Jan 2017 21:14:59 +0000 (31 13:14 -0800)
treec0a7b6b77695f9ea2b2c8c76b0a8c8f495ac77d7
parentc54ba283fa4501cc02230424ccfd84622df49256
parente459b073fb3ab8abe36e6bee5c5d6be1ed3928ae
Merge branch 'js/remote-rename-with-half-configured-remote'

With anticipatory tweaking for remotes defined in ~/.gitconfig
(e.g. "remote.origin.prune" set to true, even though there may or
may not actually be "origin" remote defined in a particular Git
repository), "git remote rename" and other commands misinterpreted
and behaved as if such a non-existing remote actually existed.

* js/remote-rename-with-half-configured-remote:
  remote rename: more carefully determine whether a remote is configured
  remote rename: demonstrate a bogus "remote exists" bug
builtin/fetch.c
builtin/remote.c
remote.c