From: Patchwork <patchwork@ipfire.org>
To: development@lists.ipfire.org
Subject: [ipfire] Patch notification: 1 patch updated
Date: Sun, 25 Feb 2018 20:20:02 +0000 [thread overview]
Message-ID: <20180225202002.30787.91096@septima.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
Hello,
The following patch (submitted by you) has been updated in Patchwork:
* ipfire: [v3] OpenVPN: New AES-GCM cipher for N2N and RW
- http://patchwork.ipfire.org/patch/1674/
- 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 reply other threads:[~2018-02-25 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 20:20 Patchwork [this message]
2018-02-26 11:20 Patchwork
2018-02-26 12:44 ` Michael Tremer
2018-03-06 16: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=20180225202002.30787.91096@septima.ipfire.org \
--to=patchwork@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