public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] unbound: Update to 1.9.0
Date: Thu, 14 Feb 2019 11:01:29 +0000	[thread overview]
Message-ID: <158112F4-0931-45C2-9BD6-2D577CBBA1D2@ipfire.org> (raw)
In-Reply-To: <a7e5bc6b-8b8a-0cc8-5227-07563452fd67@ipfire.org>

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

Hi,

> On 14 Feb 2019, at 07:05, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 13.02.2019 18:32, Michael Tremer wrote:
>> Hi,
>> 
>> I did *not* merge this one, yet.
> 
> No problem - I'm in touch with Erik trying to help testing TFO and DoT.

Please don’t forget to share what you are doing on this list :)

> 
> Its a bit weird...
> 
>> The change log that you linked wasn’t very helpful, but there was an announcement email with some more details:
>> 
>>  https://nlnetlabs.nl/pipermail/unbound-users/2019-February/011353.html
>> 
>> This release contains all the EDNS Flag Day changes and that might cause some trouble. I would prefer to merge this with the next Core Update because Core 128 should already have been closed and I do not want to risk re-opening it.
>> 
>> So, please remind me to merge this next week in case I forgot.
> 
> No hurry - I'll do. ;-)
> 
> Best,
> Matthias
> 
>> ...

-Michael

  reply	other threads:[~2019-02-14 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  9:40 Matthias Fischer
2019-02-13 17:32 ` Michael Tremer
2019-02-14  7:05   ` Matthias Fischer
2019-02-14 11:01     ` Michael Tremer [this message]
2019-02-14 17:26       ` Matthias Fischer
2019-02-15 11:34         ` Michael Tremer
2019-02-15 16:48           ` Matthias Fischer
2019-02-26  9:54             ` Michael Tremer
2019-02-15 13:12       ` 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=158112F4-0931-45C2-9BD6-2D577CBBA1D2@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