summaryrefslogtreecommitdiff
path: root/t/t4116-apply-reverse.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2009-03-16 00:35:09 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2009-03-16 00:35:09 -0700
commit9326d49412c8c154b43cb7eba2a8692e9703b0f4 (patch)
treedf13cfc93be2f22b4b58f613c778b83a7d6bf4cc /t/t4116-apply-reverse.sh
parentGive error when no remote is configured (diff)
downloadtgif-9326d49412c8c154b43cb7eba2a8692e9703b0f4.tar.xz
Remove total confusion from git-fetch and git-push
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>
Diffstat (limited to 't/t4116-apply-reverse.sh')
0 files changed, 0 insertions, 0 deletions