All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Bash <bash@genarts.com>
To: kusmabite@gmail.com
Cc: git@vger.kernel.org, jaysoffian@gmail.com, gitster@pobox.com,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH/RFC] add lame win32 credential-helper
Date: Fri, 16 Sep 2011 08:59:48 -0400 (EDT)	[thread overview]
Message-ID: <23805783.18971.1316177988773.JavaMail.root@mail.hq.genarts.com> (raw)
In-Reply-To: <CABPQNSZjGzyxJKWRDDWxRj_SLdC1Y_9TxnAMOA+b-Pw3+X-E7w@mail.gmail.com>

----- Original Message -----
> From: "Erik Faye-Lund" <kusmabite@gmail.com>
> To: "Jeff King" <peff@peff.net>
> Cc: git@vger.kernel.org, jaysoffian@gmail.com, gitster@pobox.com
> Sent: Thursday, September 15, 2011 5:48:30 PM
> Subject: Re: [PATCH/RFC] add lame win32 credential-helper
> 
> > If it's too hard to adapt it to whatever IPC
> > mechanism would be appropriate on Windows, we can just leave it out
> > on that platform.
> >
> > But the core code in git itself should be pretty straight forward.
> 
> I didn't mean that it was impossible to port, just that it didn't compile
> as-is. I haven't looked into fixing up the code so it compiles on Windows
> again myself. And I'm not really planning to; I have little git-time
> these days, and little knowledge of how unix-sockets works...

This may be common knowledge, but from our brief experiment with them last fall, Windows Named Pipes are fairly similar to Unix Domain Sockets (not named FIFOs as one would expect...).  We didn't quite get a perfect replacement using preprocessor macros, but I think you can get pretty close (we eventually dumped the idea in favor of straight TCP sockets that behave the same on all our platforms of interest).

HTH,
Stephen

  reply	other threads:[~2011-09-16 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 20:25 [PATCH/RFC] add lame win32 credential-helper Erik Faye-Lund
2011-09-15 21:40 ` Jeff King
2011-09-15 21:48   ` Erik Faye-Lund
2011-09-16 12:59     ` Stephen Bash [this message]
2011-09-30 14:42 ` Erik Faye-Lund

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=23805783.18971.1316177988773.JavaMail.root@mail.hq.genarts.com \
    --to=bash@genarts.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jaysoffian@gmail.com \
    --cc=kusmabite@gmail.com \
    --cc=peff@peff.net \
    /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.