From: Johannes Sixt <j.sixt@viscovery.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 8/6] receive-pack: Send internal errors over side-band #2
Date: Wed, 10 Feb 2010 09:13:00 +0100 [thread overview]
Message-ID: <4B726A8C.6010600@viscovery.net> (raw)
In-Reply-To: <4B725CB1.1080908@viscovery.net>
Johannes Sixt schrieb:
> Or did you replace only selected error() and warning() calls by rp_error()
> and rp_warning()?
Actually, you want to send only selected messages to the pusher. For
example, these look like errors on the server side (right?) and should go
to the site administrator:
> if (!is_null_sha1(new_sha1) && !has_sha1_file(new_sha1)) {
> - error("unpack should have generated %s, "
> - "but I can't find it!", sha1_to_hex(new_sha1));
> + rp_error("unpack should have generated %s, "
> + "but I can't find it!", sha1_to_hex(new_sha1));
> return "bad pack";
> }
> if (!old_object || !new_object ||
> old_object->type != OBJ_COMMIT ||
> new_object->type != OBJ_COMMIT) {
> - error("bad sha1 objects for %s", name);
> + rp_error("bad sha1 objects for %s", name);
> return "bad ref";
> }
> old_commit = (struct commit *)old_object;
In particular, your patch does not send errors produced by unpack-objects
or index-pack to the pusher over the sideband, and this is the right thing
to do.
-- Hannes
next prev parent reply other threads:[~2010-02-10 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 2:01 [PATCH 7/6] t5401: Use a bare repository for the remote peer Shawn O. Pearce
2010-02-10 2:01 ` [PATCH 8/6] receive-pack: Send internal errors over side-band #2 Shawn O. Pearce
2010-02-10 7:13 ` Johannes Sixt
2010-02-10 7:23 ` Junio C Hamano
2010-02-10 8:13 ` Johannes Sixt [this message]
2010-02-10 17:34 ` [PATCH 8/6 v2] " Shawn O. Pearce
2010-02-11 8:34 ` Johannes Sixt
2010-02-11 15:05 ` Shawn O. Pearce
2010-02-11 19:04 ` Johannes Sixt
2010-02-10 17:17 ` [PATCH 8/6] " Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B726A8C.6010600@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.