Junio C Hamano <gitster@xxxxxxxxx> 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... - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
