Revision 9326d49412c8c154b43cb7eba2a8692e9703b0f4 authored by Junio C Hamano on 16 March 2009, 07:35:09 UTC, committed by Junio C Hamano on 16 March 2009, 07:35:09 UTC
The config file is not the only place remotes are defined, and without consulting .git/remotes and .git/branches, you won't know if "origin" is configured by the user. Don't give up too early and insult the user with a wisecrack "Where do you want to fetch from today?" The only thing the previous patch seems to want to prevent from happening is a lazy "git fetch/push" that does not say where-from/to to produce an error message 'origin not found', and we can do that by not letting add_url_alias() to turn a nickname "origin" literally into a pathname "origin" without changing the rest of the logic. Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent fa685bd
Computing file changes ...