From: Eric Wong <normalperson@yhbt•net>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: git@vger•kernel.org
Subject: Re: [WIP/RFH/PATCH 3/3] t/lib-git-svn: adjust config to apache 2.4
Date: Thu, 9 Apr 2015 19:11:23 +0000 [thread overview]
Message-ID: <20150409191123.GA1931@dcvr.yhbt.net> (raw)
In-Reply-To: <55264763.6050703@drmicha.warpmail.net>
Michael J Gruber <git@drmicha•warpmail.net> wrote:
> So debian stable has apache 2.2? That explains why many don't see these
> problems.
Right.
> So, before 3/3, t9118 and such do run the web server and test git-svn
> against that for you?
Yes.
next prev parent reply other threads:[~2015-04-09 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:05 [PATCH 0/3] Make httpd tests run Michael J Gruber
2015-04-08 15:05 ` [PATCH 1/3] t/lib-httpd: load mod_unixd Michael J Gruber
[not found] ` <5525A208.6060807@web.de>
2015-04-09 9:27 ` Michael J Gruber
2015-04-10 3:09 ` Jeff King
2015-04-08 15:05 ` [PATCH 2/3] t/lib-git-svn: check same httpd module dirs as lib-httpd Michael J Gruber
2015-04-08 15:05 ` [WIP/RFH/PATCH 3/3] t/lib-git-svn: adjust config to apache 2.4 Michael J Gruber
2015-04-08 20:26 ` Eric Wong
2015-04-09 9:33 ` Michael J Gruber
2015-04-09 19:11 ` Eric Wong [this message]
2015-04-10 3:23 ` Jeff King
2015-04-10 3:39 ` Jeff King
2015-04-13 10:14 ` Michael J Gruber
2015-04-09 13:04 ` [PATCH 0/3] Make httpd tests run Kyle J. McKay
2015-04-09 13:14 ` Kyle J. McKay
2015-05-11 11:54 ` [PATCHv2 0/4] Make httpd tests run v2 Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 1/4] t/lib-httpd: load mod_unixd Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 2/4] t/lib-git-svn: check same httpd module dirs as lib-httpd Michael J Gruber
2015-05-11 11:54 ` [PATCH 3/4] t/t91*: do not say how to avoid the tests Michael J Gruber
2015-05-11 11:54 ` [PATCHv2 4/4 (was 3/3, still WIP)] t/lib-git-svn: adjust config to apache 2.4 WIP Michael J Gruber
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=20150409191123.GA1931@dcvr.yhbt.net \
--to=normalperson@yhbt$(echo .)net \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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