From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Pierre Habouzit <madcoder@debian.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Alex Riesen <raa.lkml@gmail.com>
Subject: Re: [PATCH v2 3/3] send-pack: assign remote errors to each ref
Date: Tue, 13 Nov 2007 17:56:08 -0800 [thread overview]
Message-ID: <7v4pfppp3b.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vbq9xpprg.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 13 Nov 2007 17:41:39 -0800")
Junio C Hamano <gitster@pobox.com> 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...
next prev parent reply other threads:[~2007-11-14 1:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 10:25 [RFC/PATCH 0/3] tracking per-ref errors on push Jeff King
2007-11-13 10:27 ` [PATCH/RFC 1/3] send-pack: track errors for each ref Jeff King
2007-11-13 11:32 ` Jeff King
2007-11-13 19:04 ` Alex Riesen
2007-11-13 22:30 ` Jeff King
2007-11-13 20:18 ` Alex Riesen
2007-11-13 10:27 ` [PATCH/RFC 2/3] send-pack: check ref->status before updating tracking refs Jeff King
2007-11-13 10:29 ` [PATCH/RFC 3/3] send-pack: assign remote errors to each ref Jeff King
2007-11-13 10:29 ` Jeff King
2007-11-13 11:34 ` [RFC/PATCH 0/3] tracking per-ref errors on push Jeff King
2007-11-13 11:36 ` [PATCH v2 1/3] send-pack: track errors for each ref Jeff King
2007-11-13 11:36 ` [PATCH v2 2/3] send-pack: check ref->status before updating tracking refs Jeff King
2007-11-13 11:37 ` [PATCH v2 3/3] send-pack: assign remote errors to each ref Jeff King
2007-11-14 1:41 ` Junio C Hamano
2007-11-14 1:56 ` Junio C Hamano [this message]
2007-11-14 2:01 ` Johannes Schindelin
2007-11-14 6:12 ` Junio C Hamano
2007-11-15 4:54 ` Jeff King
2007-11-16 5:05 ` Junio C Hamano
2007-11-15 4:47 ` Jeff King
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=7v4pfppp3b.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--cc=peff@peff.net \
--cc=raa.lkml@gmail.com \
/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.