From: Junio C Hamano <gitster@pobox.com>
To: nathan spindel <nathans@gmail.com>
Cc: "David Symonds" <dsymonds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] instaweb: if no httpd is specified and lighttpd doesn't exist, fall back on apache2.
Date: Sun, 11 May 2008 10:46:17 -0700 [thread overview]
Message-ID: <7vlk2g4tue.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <5C50F5DC-CAE4-4BF2-BCAA-8CFC8CC43C59@gmail.com> (nathan spindel's message of "Sun, 11 May 2008 10:03:34 -0700")
nathan spindel <nathans@gmail.com> writes:
> I am apathetic about which web servers are preferred, I would just
> like to see git-instaweb work well on Mac OS X. Kevin Ballard's
> suggestion was to fall back on apache2.
>
> We could also modify the default to use [lighttpd, webrick, apache2]
> in that order (whichever is available). Would the community prefer
> that approach?
I think apache is the most well known and widely used among the three, and
find Kevin's suggestion sensible.
prev parent reply other threads:[~2008-05-11 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 5:26 [PATCH] instaweb: if no httpd is specified and lighttpd doesn't exist, fall back on apache2 nathan spindel
2008-05-11 5:26 ` [PATCH] instaweb: make it compatible with Mac OS X 10.5's apache installation nathan spindel
2008-05-11 5:26 ` [PATCH] Documentation/git-instaweb.txt: Updated defaults to match my last two git-instaweb.sh changes nathan spindel
2008-05-11 6:58 ` [PATCH] instaweb: make it compatible with Mac OS X 10.5's apache installation Junio C Hamano
2008-05-11 17:11 ` nathan spindel
2008-05-11 6:44 ` [PATCH] instaweb: if no httpd is specified and lighttpd doesn't exist, fall back on apache2 Junio C Hamano
2008-05-11 17:00 ` nathan spindel
2008-05-11 18:26 ` nathan spindel
2008-05-11 11:58 ` David Symonds
2008-05-11 17:03 ` nathan spindel
2008-05-11 17:46 ` Junio C Hamano [this message]
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=7vlk2g4tue.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=nathans@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 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.