From: Johannes Sixt <j.sixt@viscovery.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] push: Use sideband channel for hook messages
Date: Fri, 05 Feb 2010 16:51:56 +0100 [thread overview]
Message-ID: <4B6C3E9C.7040009@viscovery.net> (raw)
In-Reply-To: <20100205153252.GC19255@spearce.org>
Shawn O. Pearce schrieb:
> Johannes Sixt <j.sixt@viscovery.net> wrote:
>> What would you think about passing both channels to the async callback,
>> and the communicating parties must agree on which channel they communicate
>> by closing the unused one? It would require slight changes to all current
>> async users, though. (It also requires in the threaded case that we pass
>> dup()s of the pipe channels.)
>
> Yup, I could do that. I feel like it might be over-engineering the
> solution a bit. But I'll respin the patch by splitting it apart,
> and doing a bidirectional async here, since you asked nicely.
I do agree about the over-engineering aspect. I mentioned it because in
one patch in the past Erik Faye-Lund also extended the async
infrastructure for bidirectional communication to use it in git-daemon
(Windows port). Meanwhile, he's abandoned this approach because there were
unsurmountable obstacles elsewhere; so if you introduce bidi now, it would
not immediately buy us anything.
It's your draw.
-- Hannes
next prev parent reply other threads:[~2010-02-05 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 3:37 [PATCH] push: Use sideband channel for hook messages Shawn O. Pearce
2010-02-05 5:53 ` Junio C Hamano
2010-02-05 11:58 ` Johannes Sixt
2010-02-05 15:32 ` Shawn O. Pearce
2010-02-05 15:51 ` Johannes Sixt [this message]
2010-02-05 16:14 ` Erik Faye-Lund
2010-02-05 17:29 ` Shawn O. Pearce
2010-02-05 12:07 ` Ilari Liusvaara
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=4B6C3E9C.7040009@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
/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.