From: Erik Faye-Lund <kusmabite@googlemail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] push: Use sideband channel for hook messages
Date: Fri, 5 Feb 2010 17:14:12 +0100 [thread overview]
Message-ID: <40aa078e1002050814m1edb90f8lf3d8d138fa65c332@mail.gmail.com> (raw)
In-Reply-To: <4B6C3E9C.7040009@viscovery.net>
On Fri, Feb 5, 2010 at 4:51 PM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> 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).
Just for reference, here's the latest version I wrote of that patch,
in case it's useful to have a peak at or something:
http://repo.or.cz/w/git/kusma.git/commit/682d90a174fc128910c1c8a4f81edb3cf9f0d9e2
--
Erik "kusma" Faye-Lund
next prev parent reply other threads:[~2010-02-05 16:22 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
2010-02-05 16:14 ` Erik Faye-Lund [this message]
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=40aa078e1002050814m1edb90f8lf3d8d138fa65c332@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--cc=kusmabite@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).