From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Valid til days is required with OpenVPN-2.4.x
Date: Mon, 18 Jun 2018 16:10:05 +0200 [thread overview]
Message-ID: <1529331005.8691.4.camel@ipfire.org> (raw)
In-Reply-To: <221a76d457c03149535f5eaff0270689a8388af3.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
OK, will do that. Thanks.
Best,
Erik
Am Montag, den 18.06.2018, 15:08 +0100 schrieb Michael Tremer:
> Yes, can do. Please see "next".
>
> In the future, you can create an own OpenVPN branch where all those
> proposed
> patches are collected to be able to work a little bit independent
> from me and
> also to collect patches and submit them in one go.
>
> Best,
> -Michael
>
next prev parent reply other threads:[~2018-06-18 14:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1529323219.5499.21.camel@ipfire.org>
2018-06-18 12:21 ` Tom Rymes
2018-06-18 13:09 ` Michael Tremer
2018-06-18 13:51 ` Michael Tremer
2018-06-18 14:05 ` ummeegge
2018-06-18 14:08 ` Michael Tremer
2018-06-18 14:10 ` ummeegge [this message]
2018-06-15 6:35 Erik Kapfer
2018-06-15 12:59 ` ummeegge
2018-06-17 18:14 ` Michael Tremer
2018-06-18 7:56 ` ummeegge
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=1529331005.8691.4.camel@ipfire.org \
--to=ummeegge@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