From: Erik Faye-Lund <kusmabite@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Heiko Voigt" <hvoigt@hvoigt.net>,
"Git List" <git@vger.kernel.org>,
"Duy Nguyen" <pclouds@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Torsten Bögershausen" <tboegi@web.de>,
"Robert Zeh" <robert.allan.zeh@gmail.com>,
"Jeff King" <peff@peff.net>,
"Karsten Blees" <karsten.blees@gmail.com>,
"Drew Northup" <n1xim.email@gmail.com>
Subject: Re: [RFC/PATCH] Documentation/technical/api-fswatch.txt: start with outline
Date: Tue, 12 Mar 2013 10:50:15 +0100 [thread overview]
Message-ID: <CABPQNSYT2DiMeMe+6ropa8O7YUzAVR_b4CD+75qw4fw6XAv+8w@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0m+CS25=Z91y90z49g4GK+b7oFugiXoH0h0J6P-yQXRCQ@mail.gmail.com>
On Tue, Mar 12, 2013 at 10:43 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Heiko Voigt wrote:
>> While talking about platform independence. How about Windows? AFAIK
>> there are no file based sockets. How about using shared memory, thats
>> available, instead? It would greatly reduce the needed porting effort.
>
> What about the git credential helper: it uses UNIX sockets, no? How
> does git-credential-winstore [1] work?
>
> [1]: https://github.com/anurse/git-credential-winstore
First, we have a proper credential helper for Windows in
contrib/credential/wincred these days. As the one who wrote that, we
communicate using stdin/stdout. The credential-helper doesn't maintain
state in itself, the Windows Credential Manager does. I suspect
git-credential-winstore works the same way.
As for Windows support, AFAIK there is no support for Unix domain
sockets in Windows. But there is support for named pipes, which is
almost the same thing. What we have support for in compat/mingw.[ch]
is a different matter, but we can extend that if needed.
next prev parent reply other threads:[~2013-03-12 9:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 20:17 [RFC/PATCH] Documentation/technical/api-fswatch.txt: start with outline Ramkumar Ramachandra
2013-03-11 17:05 ` Heiko Voigt
2013-03-12 9:43 ` Ramkumar Ramachandra
2013-03-12 9:50 ` Erik Faye-Lund [this message]
2013-03-12 9:55 ` Jeff King
2013-03-12 23:21 ` Karsten Blees
2013-03-13 1:03 ` Duy Nguyen
2013-03-13 17:50 ` Karsten Blees
2013-03-13 19:38 ` Junio C Hamano
2013-03-14 10:58 ` Duy Nguyen
2013-03-15 16:27 ` Pete Wyckoff
2013-03-16 14:21 ` Thomas Rast
2013-03-18 8:24 ` Ramkumar Ramachandra
2013-03-18 10:07 ` Thomas Rast
2013-03-25 10:44 ` Ramkumar Ramachandra
2013-03-25 10:59 ` Duy Nguyen
2013-03-25 11:13 ` Ramkumar Ramachandra
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=CABPQNSYT2DiMeMe+6ropa8O7YUzAVR_b4CD+75qw4fw6XAv+8w@mail.gmail.com \
--to=kusmabite@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=karsten.blees@gmail.com \
--cc=n1xim.email@gmail.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=robert.allan.zeh@gmail.com \
--cc=tboegi@web.de \
/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).