From: Erik Faye-Lund <kusmabite@googlemail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Avery Pennarun <apenwarr@gmail.com>,
"Anthony W. Youngman" <wol@thewolery.demon.co.uk>,
git@vger.kernel.org
Subject: Re: Common setting for interoperability repo across windows and unix?
Date: Thu, 5 Nov 2009 00:10:28 +0100 [thread overview]
Message-ID: <40aa078e0911041510p645c37c3i238fbf0eb568aba0@mail.gmail.com> (raw)
In-Reply-To: <20091104230122.GK10505@spearce.org>
On Thu, Nov 5, 2009 at 12:01 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Avery Pennarun <apenwarr@gmail.com> wrote:
>> >
>> > git-daemon doesn't (currently) work on msysgit. Currently I run git-daemon
>> > on my linpus netbook and pull/push from windows.
>>
>> I didn't know that. Windows sockets are mercifully very nearly
>> compatible with Linux ones, so hopefully this wouldn't be too hard to
>> fix for someone that needs it. (Not me; I prefer cygwin over msys in
>> all cases.)
>
> git-daemon relies on fork, do work, then later exec. Windows lacks
> this concept. Making it hard to port.
Before anyone starts hacking: I've got a working git-daemon on
Windows, based on some old patches from Mike Pape, plus some extending
of the start_async-api. It's still not ready for submission, but I
think I've got the last important technical details nailed down now,
all that is needed is a fair share of clean-up. Hopefully I'll have it
ready for submission during the week-end some time.
--
Erik "kusma" Faye-Lund
next prev parent reply other threads:[~2009-11-04 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:09 Common setting for interoperability repo across windows and unix? Dilip M
2009-11-03 15:33 ` Avery Pennarun
2009-11-04 21:45 ` Anthony W. Youngman
2009-11-04 22:59 ` Avery Pennarun
2009-11-04 23:01 ` Shawn O. Pearce
2009-11-04 23:10 ` Erik Faye-Lund [this message]
2009-11-04 0:46 ` Vietor Liu
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=40aa078e0911041510p645c37c3i238fbf0eb568aba0@mail.gmail.com \
--to=kusmabite@googlemail.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=spearce@spearce.org \
--cc=wol@thewolery.demon.co.uk \
/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).