http-push: using error() and warning() as appropriate
Change three occurences of using inconsistent error/warning reporting by using the relevant error() / warning() calls to be consitent with the rest of the code. Signed-off-by: Miklos Vajna <vmiklos@frugalware.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Miklos Vajna committed
Mar 24, 2009 at 02:09 UTC
d5c87cb4ffc411fc12dbc261af3ed29633e49fba
1 file changed
+3
-3
http-push.c
+3
-3
@@ -759,7 +759,7 @@ static void finish_request(struct transfer_request *request)
759
}
760
} else {
761
if (request->http_code == 416)
762
- fprintf(stderr, "Warning: requested range invalid; we may already have all the data.\n");
762
+ warning("requested range invalid; we may already have all the data.");
763
764
git_inflate_end(&request->stream);
765
git_SHA1_Final(request->real_sha1, &request->c);
@@ -1616,7 +1616,7 @@ static int locking_available(void)
1616
}
1617
XML_ParserFree(parser);
1618
if (!lock_flags)
1619
- error("Error: no DAV locking support on %s",
1619
+ error("no DAV locking support on %s",
1620
remote->url);
1621
1622
} else {
@@ -2225,7 +2225,7 @@ int main(int argc, char **argv)
2225
if (info_ref_lock)
2226
remote->can_update_info_refs = 1;
2227
else {
2228
- fprintf(stderr, "Error: cannot lock existing info/refs\n");
2228
+ error("cannot lock existing info/refs");
2229
rc = 1;
2230
goto cleanup;
2231
}