From: Charles Brown <cab_77573@yahoo.com>
To: development@lists.ipfire.org
Subject: Fwd: Merge request for ipblocklist
Date: Fri, 08 Jul 2022 10:42:03 -0500 [thread overview]
Message-ID: <5352a1d9-cba5-24f7-97e7-23db37a21724@yahoo.com> (raw)
In-Reply-To: <f9517379-1083-25e8-1e94-30e5603106d8@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hello Stefan,
For those of us running your test version from
"https://people.ipfire.org/~stevee/ipblocklist",
is there any cleanup that needs to be done when transitioning from your
test version to the new Core Update 170 baseline version?
-Charles
> On 7 Jul 2022, at 17:42, Stefan Schantl<stefan.schantl(a)ipfire.org> wrote:
>
> 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-08 15:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f9517379-1083-25e8-1e94-30e5603106d8@yahoo.com>]
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=5352a1d9-cba5-24f7-97e7-23db37a21724@yahoo.com \
--to=cab_77573@yahoo.com \
--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