From: Wolfgang Apolinarski <wolfgang@apolinarski.de>
To: development@lists.ipfire.org
Subject: Update to Apache 2.4
Date: Fri, 21 Apr 2017 18:43:55 +0200 [thread overview]
Message-ID: <002e01d2babe$7770f610$6652e230$@apolinarski.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
Hi,
finally, I was able to at least split the patch into two pieces (not four as written before), one containing apr and aprutil (which
will also work together with apache 2.2 (that - in contrast to apache 2.4 - contains an embedded version of apr that will be
deactivated in this case)), the other one contains apache 2.4 and the updated configuration files.
It needed more time than expected, because I rebuilt the IPFire image several times to make sure that the patches are actually
working.
Best regards,
Wolfgang
PS.: I will use my Google-Account to send the patches.
reply other threads:[~2017-04-21 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002e01d2babe$7770f610$6652e230$@apolinarski.de' \
--to=wolfgang@apolinarski.de \
--cc=development@lists.ipfire.org \
/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