From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Updated: Enable ipv6 addresses in Firewall logs
Date: Fri, 08 Jan 2016 22:30:32 +0100 [thread overview]
Message-ID: <56902A78.2050007@ipfire.org> (raw)
In-Reply-To: <1452210265.4749.12.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
Hi,
On 08.01.2016 00:44, Michael Tremer wrote:
> @Matthias: Could you maybe review and test this patch in a non-IPv6
> setup?
I'll take a look... ;-)
Best,
Matthias
prev parent reply other threads:[~2016-01-08 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 12:00 [PATCH] " Michael Eitelwein
2016-01-07 18:53 ` [PATCH] Updated: " Michael Eitelwein
2016-01-07 23:44 ` Michael Tremer
2016-01-08 21:30 ` Matthias Fischer [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=56902A78.2050007@ipfire.org \
--to=matthias.fischer@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