From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [ipfire] Patch notification: 1 patch updated
Date: Mon, 26 Feb 2018 12:44:44 +0000 [thread overview]
Message-ID: <1519649084.5664.35.camel@ipfire.org> (raw)
In-Reply-To: <20180226112002.22724.56254@septima.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
Hello guys,
that patchwork is sending these emails is a side-effect of our DMARC deployment.
I am looking into how to fix this soon.
https://bugzilla.ipfire.org/show_bug.cgi?id=11639
-Michael
On Mon, 2018-02-26 at 11:20 +0000, Patchwork via Development wrote:
> Hello,
>
> The following patch (submitted by you) has been updated in Patchwork:
>
> * ipfire: OpenVPN: Ship missing OpenSSL configuration file for update
> - http://patchwork.ipfire.org/patch/1675/
> - for: IPFire
> was: New
> now: Staged
>
> This email is a notification only - you do not need to respond.
>
> Happy patchworking.
>
> --
>
> This is an automated mail sent by the Patchwork system at
> patchwork.ipfire.org. To stop receiving these notifications, edit
> your mail settings at:
> http://patchwork.ipfire.org/mail/
next prev parent reply other threads:[~2018-02-26 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 11:20 Patchwork
2018-02-26 12:44 ` Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 16:20 Patchwork
2018-02-25 20:20 Patchwork
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=1519649084.5664.35.camel@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