public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: ipblacklist V2
Date: Mon, 07 Feb 2022 10:31:34 +0000	[thread overview]
Message-ID: <1DC94D84-CE41-4A42-8195-27E14E542AAA@ipfire.org> (raw)
In-Reply-To: <stjqk4$v1j$1@tuscan3.grantura.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

Hello Rob,

Thank you for your interest in working on this.

Yes, I always thought that there was great interest in moving this over the line. However, I could not find where we left off here.

There were a couple of outstanding issues that had to be resolved. I just couldn’t find my last emails. Are you aware of these?

-Michael

> On 4 Feb 2022, at 18:17, Rob Brewer <ipfire-devel(a)grantura.co.uk> wrote:
> 
> Hi.
> 
> I have been looking at Tim FitzGeorge's code for ipblacklist v2 on 
> https://patchwork.ipfire.org/project/ipfire/list/?series=1215 to see if I 
> can help progress its incorporation into IPFire.
> After I extracted the programs from Patchwork I have been able to build them 
> into my firewall where they are running very successfully.
> The code on the server seems to be in good shape and apart from a few small 
> patches and additions of a few missing scripts I think it could be 
> successfully introduced into the IPFire code base.
> I am more than happy to help in seeing this process carried out but need to 
> know if this is acceptable to yourselves.
> 
> Regards
> Rob Brewer


  reply	other threads:[~2022-02-07 10:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 18:17 Rob Brewer
2022-02-07 10:31 ` Michael Tremer [this message]
2022-02-07 12:58   ` Rob Brewer
2022-02-09 14:38     ` Adolf Belka
2022-02-09 21:43       ` Rob Brewer
2022-02-09 22:14         ` Adolf Belka
2022-02-10  9:45           ` Michael Tremer
2022-02-09 13:23   ` Rob Brewer
2022-02-09 14:29     ` Adolf Belka
2022-02-10  9:41     ` Michael Tremer
2022-02-10 15:12       ` Rob Brewer
2022-02-10 16:48         ` Michael Tremer
2022-02-12 21:29           ` Tim FitzGeorge
2022-02-13 12:44             ` Rob Brewer
2022-02-15 12:58               ` Michael Tremer
2022-02-15 12:54             ` Michael Tremer
     [not found] <ef8ac1dcde46b22207dde653d6717a95d2a737e7.camel@ipfire.org>
2022-03-01 13:13 ` Michael Tremer
2022-03-01 16:08 ` Rob Brewer
2022-03-05 18:52 ` Stefan Schantl
2022-03-05 21:46   ` Rob Brewer
2022-03-07 20:39     ` Michael Tremer
2022-03-07 22:54       ` Rob Brewer
2022-03-08 10:59         ` Rob Brewer
2022-03-08 15:45           ` Michael Tremer
2022-04-03  9:16           ` Stefan Schantl
2022-04-03 21:09             ` Rob Brewer

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=1DC94D84-CE41-4A42-8195-27E14E542AAA@ipfire.org \
    --to=michael.tremer@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