Re: Git-aware HTTP transport
- Date: Thu, 28 Aug 2008 23:50:25 -0700
- From: Junio C Hamano <gitster@xxxxxxxxx>
- Subject: Re: Git-aware HTTP transport
"H. Peter Anvin" <hpa@xxxxxxxxx> writes: > We should be able to detect either inconsistency, or lack of forward > progress, but as long as there is forward progress made there doesn't > seem to be a strong need to terminate. Yeah, what I wanted to say was that it would be tricky to detect (any/lack of) forward progress without having server side state and without trusting the client. -- 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
- Follow-Ups:
- Re: Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- References:
- Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- From: H. Peter Anvin
- Re: Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- From: H. Peter Anvin
- Re: Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- From: H. Peter Anvin
- Re: Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- From: Junio C Hamano
- Re: Git-aware HTTP transport
- From: Shawn O. Pearce
- Re: Git-aware HTTP transport
- From: Junio C Hamano
- Re: Git-aware HTTP transport
- From: H. Peter Anvin
- Git-aware HTTP transport
- Prev by Date: Re: [PATCH 2/2 - RFH/WIP] xdiff-merge: optionally show conflicts in "diff3 -m" style
- Next by Date: Re: Future suggestion's to assist with changes to git.
- Previous by thread: Re: Git-aware HTTP transport
- Next by thread: Re: Git-aware HTTP transport
- Index(es):