public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Merge request for ipblocklist
Date: Sun, 10 Jul 2022 10:02:26 +0000	[thread overview]
Message-ID: <c34528e8-7280-683a-046c-d87752e4afa3@ipfire.org> (raw)
In-Reply-To: <e4a2996cffdfb754be8f4d3a0800dd09d662d826.camel@ipfire.org>

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

Hello Stefan,

thanks for your mail and submitting this merge request.

I merged the branch of yours with commit d574941b906199d286c49159f2b11a6e5f85411b, and
ship all the things I deem necessary with commit fc842bf1c0b9e04e650a483d044e1174fc6ddcb7.

As for the latter, it would be great if you could have a look at it and drop me a line,
should anything be missing or wrong in there.

Thanks in advance, and best regards,
Peter Müller

> Hello Peter, hello list followers,
> 
> this is a merge request for the ipblocklist feature to get part of core
> update 170.
> 
> The development for the main parts has been done, the feature works
> stable and several testing feedback for the testing releases is
> available.
> 
> I've rebased the branch against the current next and pushed it into my
> personal git repository as "ipblocklist-final".
> 
> Peter please have a look on it and if everything is okay, please merge
> it so we finally can release it.
> 
> Thanks in advance,
> 
> -Stefan
> 

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 15:42 Stefan Schantl
2022-07-08  8:54 ` Michael Tremer
2022-07-10 10:02 ` Peter Müller [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=c34528e8-7280-683a-046c-d87752e4afa3@ipfire.org \
    --to=peter.mueller@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