All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Dmitry Ivankov <divanorama@gmail.com>,
	Jeff King <peff@peff.net>,
	Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH/RFC] remote-helpers: set up a pipe to read fast-import response
Date: Wed, 11 Apr 2012 09:10:09 -0700	[thread overview]
Message-ID: <7v1ununtb2.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120411143249.GA4140@burratino> (Jonathan Nieder's message of "Wed, 11 Apr 2012 09:32:49 -0500")

Jonathan Nieder <jrnieder@gmail.com> writes:

> Something like this patch was sitting in my tree gathering moss but I
> quite like it so I thought I should send it out for feedback.
>
> I can't seem to find any copy of this patch in the list archives.
> Maybe I received it by private email.  Dmitry, do you remember better?
>
> Can also be found at
>
>   git://repo.or.cz/git/jrn.git topics/di/remote-helper-blob-access
>
> and will be part of the svn-fe-pu branch there in the next push.

Does this essentially connect the frontend and fast-import via
bidirectional pipes?  How is the flow control and deadlock avoidance
supposed to happen (I guess the side that wants to give a command to ask
for information needs to wait until it reads everything from the other
side to drain the pipe before doing so), and isn't it something that need
to be documented?

  reply	other threads:[~2012-04-11 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 14:32 [PATCH/RFC] remote-helpers: set up a pipe to read fast-import response Jonathan Nieder
2012-04-11 16:10 ` Junio C Hamano [this message]
2012-04-11 17:17   ` [PATCH/RFC] fast-import doc: deadlock avoidance in bidirectional mode Jonathan Nieder
2012-04-11 17:32     ` Junio C Hamano
2012-04-11 21:25       ` [PATCH/RFC v2] fast-import doc: cat-blob and ls responses need to be consumed quickly Jonathan Nieder
2012-04-11 21:32         ` Junio C Hamano
2012-04-11 21:46           ` Jonathan Nieder

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=7v1ununtb2.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=divanorama@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    --cc=srabbelier@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.