From: Michael J Gruber <git@drmicha•warpmail.net>
To: Eric Wong <normalperson@yhbt•net>, Jeff King <peff@peff•net>
Cc: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: Re: What's cooking in git.git (Jan 2016, #02; Mon, 11)
Date: Tue, 19 Jan 2016 08:07:23 +0100 [thread overview]
Message-ID: <569DE0AB.9050403@drmicha.warpmail.net> (raw)
In-Reply-To: <20160118213957.GA25460@dcvr.yhbt.net>
Eric Wong venit, vidit, dixit 18.01.2016 22:39:
> Jeff King <peff@peff•net> wrote:
>> On Mon, Jan 18, 2016 at 02:35:24PM +0100, Michael J Gruber wrote:
>>> Junio C Hamano venit, vidit, dixit 12.01.2016 00:45:
>>>>
>>>> * mg/httpd-tests-update-for-apache-2.4 (2015-04-08) 2 commits
>
>>>> Will discard.
>>>
>>> Oh, sorry. Work killing me plus I was waiting for help, too.
>>
>> FWIW, I took a look at them a few months ago, but I couldn't reproduce
>> the problems in the first place. I think it has to do with the default
>> apache setup given by my system (debian unstable) versus others.
>
> Ugh, I was meaning to look into these too (after upgrading to
> Debian Jessie), but maybe it needs to be tested on Fedora/RH-based
> configs?
It needs to be tested with a "default config" I think, in the sense of
"apache 2.4 default". Fedora seems to use the default config which is
different from earlier apaches' defaults.
Debian uses a config which is not the 2.4 default but makes switching
from earlier apaches easier.
Back then, I was only able to get half way to running the git svn tests
over http. I think I got our test suite to start http and run the git
over http tests that didn't run before on Fedora, but I couldn't get git
svn over http tests to run (so that they are run via local protocol
instead). I'll keep it in mind, though.
Michael
next prev parent reply other threads:[~2016-01-19 7:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 23:45 What's cooking in git.git (Jan 2016, #02; Mon, 11) Junio C Hamano
2016-01-12 0:06 ` Mike Hommey
2016-01-12 3:04 ` Junio C Hamano
2016-01-12 4:34 ` Edmundo Carmona Antoranz
2016-01-12 8:39 ` Johannes Schindelin
2016-01-12 18:47 ` Junio C Hamano
2016-01-12 21:49 ` Jeff King
2016-01-13 23:07 ` Junio C Hamano
2016-01-13 23:22 ` Jeff King
2016-01-13 23:44 ` Junio C Hamano
2016-01-13 23:54 ` Junio C Hamano
2016-01-14 10:21 ` Jeff King
2016-01-13 2:56 ` David A. Greene
2016-01-18 13:35 ` Michael J Gruber
2016-01-18 17:06 ` Jeff King
2016-01-18 21:39 ` Eric Wong
2016-01-19 7:07 ` Michael J Gruber [this message]
2016-01-25 9:56 ` Duy Nguyen
2016-01-25 22:03 ` Junio C Hamano
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=569DE0AB.9050403@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=normalperson@yhbt$(echo .)net \
--cc=peff@peff$(echo .)net \
/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