| commit | 39a570f26c953e8277a6a26c00da657b240dcdd4 | |
| author | Jeff King <peff@peff.net> | |
| Fri, 5 Apr 2013 22:22:01 +0000 (5 18:22 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 7 Apr 2013 01:56:45 +0000 (6 18:56 -0700) | ||
| tree | 1e3aaf554d71abf2d7f1221522af74cd6a155f73 | treesnapshot (tar.gz zip) |
| parent | 67d2a7b5c502496b0c5acd25a5e0ffa766b61745 | commitdiff |
http: re-word http error message
When we report an http error code, we say something like:
error: The requested URL reported failure: 403 Forbidden while accessing http://example.com/repo.git
Everything between "error:" and "while" is written by curl,
and the resulting sentence is hard to read (especially
because there is no punctuation between curl's sentence and
the remainder of ours). Instead, let's re-order this to give
better flow:
error: unable to access 'http://example.com/repo.git: The requested URL reported failure: 403 Forbidden
This is still annoyingly long, but at least reads more
clearly left to right.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When we report an http error code, we say something like:
error: The requested URL reported failure: 403 Forbidden while accessing http://example.com/repo.git
Everything between "error:" and "while" is written by curl,
and the resulting sentence is hard to read (especially
because there is no punctuation between curl's sentence and
the remainder of ours). Instead, let's re-order this to give
better flow:
error: unable to access 'http://example.com/repo.git: The requested URL reported failure: 403 Forbidden
This is still annoyingly long, but at least reads more
clearly left to right.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| http.c | diffblobblamehistory |