From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Fix upload check for root and host certificate
Date: Tue, 19 Jun 2018 11:40:11 +0100 [thread overview]
Message-ID: <1af87fe2ca49bbdf2760942ee2f8d1e4c5d8ebab.camel@ipfire.org> (raw)
In-Reply-To: <1529339453.8691.9.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
?
On Mon, 2018-06-18 at 18:30 +0200, ummeegge wrote:
> upps got a lot of conflicts,
> but got an mail from patchwork that the last two patches has been
> updated ? Should i nevertheless go for another commit ?
>
> And yes we are on (IP)Fire :D ,
>
> Best,
>
> Erik
>
> Am Montag, den 18.06.2018, 16:52 +0100 schrieb Michael Tremer:
> > Actually. It doesn't apply against next... Can you check why?
> >
> > On Mon, 2018-06-18 at 16:46 +0100, Michael Tremer wrote:
> > >
> > > Merged.
> > >
> > > We are on fire today!
> > >
>
>
next prev parent reply other threads:[~2018-06-19 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 15:10 Erik Kapfer
2018-06-18 15:46 ` Michael Tremer
2018-06-18 15:52 ` Michael Tremer
2018-06-18 16:30 ` ummeegge
2018-06-19 10:40 ` Michael Tremer [this message]
2018-06-19 12:02 ` ummeegge
2018-06-19 13:01 ` Michael Tremer
2018-06-19 14:10 ` 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=1af87fe2ca49bbdf2760942ee2f8d1e4c5d8ebab.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