On Tue, Nov 12, 2013 at 10:33:49AM -0800, H. Peter Anvin wrote:
> > Which means that your original wish may not be granted with
> > SO_KEEPALIVE at all, no? I was wondering if you wanted a forced
> > timeout based on alarm(2), something similar to what you added to
> > git-daemon in 960deccb (git
On 11/12/2013 09:45 AM, Junio C Hamano wrote:
> "H. Peter Anvin" writes:
>
>> On 11/10/2013 12:17 PM, Eric Wong wrote:
>>> "H. Peter Anvin" wrote:
When a remote server is unavailable or very slow, some git commands can
stall out indefinitely. It would be a very good thing if remote
>>
"H. Peter Anvin" writes:
> On 11/10/2013 12:17 PM, Eric Wong wrote:
>> "H. Peter Anvin" wrote:
>>> When a remote server is unavailable or very slow, some git commands can
>>> stall out indefinitely. It would be a very good thing if remote
>>> commands -- but especially git fetch -- could be giv
On 11/10/2013 12:17 PM, Eric Wong wrote:
> "H. Peter Anvin" wrote:
>> When a remote server is unavailable or very slow, some git commands can
>> stall out indefinitely. It would be a very good thing if remote
>> commands -- but especially git fetch -- could be given a timeout.
>
> We've had SO_K
"H. Peter Anvin" wrote:
> When a remote server is unavailable or very slow, some git commands can
> stall out indefinitely. It would be a very good thing if remote
> commands -- but especially git fetch -- could be given a timeout.
We've had SO_KEEPALIVE on git and ssh transports since e47a8583
When a remote server is unavailable or very slow, some git commands can
stall out indefinitely. It would be a very good thing if remote
commands -- but especially git fetch -- could be given a timeout.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a
6 matches
Mail list logo
