summaryrefslogtreecommitdiff
path: root/Documentation/gitrevisions.txt
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2014-07-09 17:47:20 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-07-10 10:54:22 -0700
commitcdaa4e98ca56586f78a455bd624457248347a56d (patch)
tree1f69628ae28d8eed9d7453d5c3916bdc44e33ed4 /Documentation/gitrevisions.txt
parentremote-curl: use error instead of fprintf(stderr) (diff)
downloadtgif-cdaa4e98ca56586f78a455bd624457248347a56d.tar.xz
remote-curl: mark helper-protocol errors more clearly
When we encounter an error in remote-curl, we generally just report it to stderr. There is no need for the user to care that the "could not connect to server" error was generated by git-remote-https rather than a function in the parent git-fetch process. However, when the error is in the protocol between git and the helper, it makes sense to clearly identify which side is complaining. These cases shouldn't ever happen, but when they do, we can make them less confusing by being more verbose. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/gitrevisions.txt')
0 files changed, 0 insertions, 0 deletions