Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:50

Junio C Hamano [off-list ref] writes:
quoted
  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...
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help