public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Fix upload check for root and host certificate
Date: Mon, 18 Jun 2018 18:30:53 +0200	[thread overview]
Message-ID: <1529339453.8691.9.camel@ipfire.org> (raw)
In-Reply-To: <5121e7d81cb89be67bebf63874d8573ba32b507f.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 441 bytes --]

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!
> > 


  reply	other threads:[~2018-06-18 16:30 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 [this message]
2018-06-19 10:40       ` Michael Tremer
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=1529339453.8691.9.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