From: Charles Brown <cab_77573@yahoo.com>
To: development@lists.ipfire.org
Subject: Re: Possible IPS Related Issues with Cure Update 1664
Date: Wed, 02 Mar 2022 07:14:37 -0600 [thread overview]
Message-ID: <c543b314-edd7-16a1-e87c-f454c35cbd8e@yahoo.com> (raw)
In-Reply-To: <193f31b4-8118-8ab0-8df7-1549d6d5bd3a@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
https://bugzilla.ipfire.org/show_bug.cgi?id=12785
On 3/2/2022 7:11 AM, Charles Brown wrote:
> Recent community forum posts indicate there may be an issue or two
> around IPS with Core Update 164
> ...
> https://bugzilla.ipfire.org/buglist.cgi?chfieldfrom=24h&list_id=17975
>
> Just sharing,
> Charles Brown
>
next prev parent reply other threads:[~2022-03-02 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <193f31b4-8118-8ab0-8df7-1549d6d5bd3a.ref@yahoo.com>
2022-03-02 13:11 ` Charles Brown
2022-03-02 13:14 ` Charles Brown [this message]
2022-03-02 15:38 ` Michael Tremer
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=c543b314-edd7-16a1-e87c-f454c35cbd8e@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