From: Wolfgang Apolinarski <wolfgang.apolinarski@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/1] Apache: Update to 2.4.34
Date: Tue, 17 Jul 2018 20:13:29 +0200 [thread overview]
Message-ID: <20180717181330.24801-1-wolfgang.apolinarski@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 248 bytes --]
Apache: Update to 2.4.34
- Small bugfix release, apr and apr-util are still up-to-date.
- Built and tested.
Wolfgang Apolinarski (1):
Apache: Update to 2.4.34
lfs/apache2 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.13.0
next reply other threads:[~2018-07-17 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 18:13 Wolfgang Apolinarski [this message]
2018-07-17 18:13 ` [PATCH 1/1] " Wolfgang Apolinarski
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=20180717181330.24801-1-wolfgang.apolinarski@ipfire.org \
--to=wolfgang.apolinarski@ipfire.org \
--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