From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref Date: Tue, 13 Nov 2007 17:56:08 -0800 Message-ID: <7v4pfppp3b.fsf@gitster.siamese.dyndns.org> References: <20071113102500.GA2767@sigill.intra.peff.net> <20071113113710.GC15880@sigill.intra.peff.net> <7vbq9xpprg.fsf@gitster.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git@vger.kernel.org, Pierre Habouzit , Daniel Barkalow , Alex Riesen To: Jeff King X-From: git-owner@vger.kernel.org Wed Nov 14 02:58:12 2007 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1Is7Vt-0007dr-5g for gcvg-git-2@gmane.org; Wed, 14 Nov 2007 02:57:57 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759110AbXKNB4e (ORCPT ); Tue, 13 Nov 2007 20:56:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759218AbXKNB4e (ORCPT ); Tue, 13 Nov 2007 20:56:34 -0500 Received: from sceptre.pobox.com ([207.106.133.20]:42237 "EHLO sceptre.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759110AbXKNB4c (ORCPT ); Tue, 13 Nov 2007 20:56:32 -0500 Received: from sceptre (localhost.localdomain [127.0.0.1]) by sceptre.pobox.com (Postfix) with ESMTP id 915A52F0; Tue, 13 Nov 2007 20:56:52 -0500 (EST) Received: from pobox.com (ip68-225-240-77.oc.oc.cox.net [68.225.240.77]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by sceptre.sasl.smtp.pobox.com (Postfix) with ESMTP id F2ED49588B; Tue, 13 Nov 2007 20:56:46 -0500 (EST) In-Reply-To: <7vbq9xpprg.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 13 Nov 2007 17:41:39 -0800") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano writes: >> 2. the status parsing is not foolproof. We get a line like >> >> ng refs/heads/master arbitrary msg >> >> which cannot be parsed unambiguously... > > Is it really "arbitrary msg", or just a fixed set of strings? This was a wrong thing to say. We may add new error message in later versions of receive-pack and we want to make it compatible with today's send-pack with minimum hassle. So that is a problem. But... > Also I think we can rely on the order report-status extension > reports the per-ref result. It gives back the information the > same order send-pack side supplies the head information, no? I was hoping that this can solve both of the problems you cited...