From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: pascal@obry.net
Cc: Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
Tim Visher <tim.visher@gmail.com>,
Tariq Hassanen <tariq.hassanen@gmail.com>,
git@vger.kernel.org
Subject: Re: Using Git with windows
Date: Mon, 09 Mar 2009 18:29:25 +0000 [thread overview]
Message-ID: <49B56005.5010802@ramsay1.demon.co.uk> (raw)
In-Reply-To: <49B2C529.6010002@obry.net>
Pascal Obry wrote:
> Robin Rosenberg a écrit :
>> I think that worked fine when I tried using cygwin's apache. Mixing a cygwin
>> git with a win32 apache did not work well.
>
> Well, I tried with lighttpd IIRC. I do not want Apache just for browsing
> a Git repo.
>
Pascal, I also installed lighttpd on cygwin, just so that I could test gitweb
and cgit (I have Apache installed on Linux). I had a few problems getting it
to work at first. Only later did I notice that "git-instaweb" didn't work.
Having fixed the installation problems earlier, I fixed git-instaweb and then
forgot to send in the patch. Oops... Patch on the way... ;-)
[I had intended to make several other changes and submit it later...]
You may also notice that "git-instaweb" does not provide the git-logo.png
and git-favicon.png; so if that bothers you, just copy those files from
your git repo into the target repo's .git/gitweb directory. (That was one
of the things I was going to look at fixing)
<off-topic>
Note: if you decide to try cgit, then be aware that lighttpd has a bug which
causes problems with mixed-case pathnames in the pathinfo. lighttpd down-cases
the filename part of the pathinfo when on a case insensitive filesystem, so
cgit can't find the corresponding blob. (This is not a problem with gitweb).
I sent a fix for this bug to (who I thought was) the lighttpd maintainer, but
didn't get any response; so don't count on a fix for this.
An amusing, but impractical, workaround for this is to name your document root
something like /123 ie the path is numeric (and so does not differ in case ;-)
[lighttpd uses a runtime test of the case-sensitive-ness of the document root
pathname to control this behaviour]
Also, I could not get lighttpd to execute a cgi program with an ".exe" extension
so I had to create a simple script, viz:
$ cat /var/www/cgit/cgit.cgi
#!/bin/sh
exec /var/www/cgit/cgit.cgi.exe
$
<off-topic>
ATB,
Ramsay Jones
next prev parent reply other threads:[~2009-03-09 18:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e878dbad0903052321l6c0d310bk2ba568138b409d36@mail.gmail.com>
2009-03-06 7:23 ` Using Git with windows Tariq Hassanen
2009-03-06 8:16 ` John Chapman
2009-03-06 10:59 ` Johannes Schindelin
2009-03-06 14:38 ` Tim Visher
2009-03-06 15:30 ` Dmitry Potapov
2009-03-07 17:58 ` Pascal Obry
2009-03-07 18:00 ` Pascal Obry
2009-03-07 19:02 ` Robin Rosenberg
2009-03-07 19:04 ` Pascal Obry
2009-03-09 18:29 ` Ramsay Jones [this message]
2009-03-06 19:10 John Dlugosz
2009-03-07 2:50 ` Johannes Schindelin
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=49B56005.5010802@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=git@vger.kernel.org \
--cc=pascal@obry.net \
--cc=robin.rosenberg.lists@dewire.com \
--cc=tariq.hassanen@gmail.com \
--cc=tim.visher@gmail.com \
/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).