From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: A few updates - built under Core 120
Date: Thu, 03 May 2018 18:08:30 +0100 [thread overview]
Message-ID: <1525367310.2479471.305.camel@ipfire.org> (raw)
In-Reply-To: <47c79f5e-ff16-d6cc-f77d-7e143a672fda@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Perfect. Keep them coming. It is good to bundle them together and align the
patches a little with the release schedule of the Core Updates though.
Also, please try to encourage people to review and *test*. We need to have more
eyeballs on the patches that we merge than just mine.
Best,
-Michael
On Thu, 2018-05-03 at 19:01 +0200, Matthias Fischer wrote:
> Hi,
>
> as I wrote, current 'next' won't build for me - it still doesn't.
>
> So I prepared the following updates under Core 119 / Core 120:
>
> pcre => 8.4.2
> libidn => 1.34
> nano => 2.9.6
> htop => 2.2.0
> openssh => 7.7.p1
> unbound => 1.7.1
>
> All of these are running here, patches follow.
>
> If anyone has any concerns about this, please let me know.
>
> Best,
> Matthias
next prev parent reply other threads:[~2018-05-03 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 17:01 Matthias Fischer
2018-05-03 17:08 ` Michael Tremer [this message]
2018-05-03 18:19 ` Peter Müller
2018-05-03 19:34 ` Michael Tremer
2018-05-04 20:13 ` Matthias Fischer
2018-05-04 20:19 ` Matthias Fischer
2018-05-05 17:50 ` 'next' with new kernel 4.14.39 took a long time - (was: Re: A few updates - built under Core 120) Matthias Fischer
2018-05-06 22:55 ` 'next' with new kernel 4.14.39 took a long time - Matthias Fischer
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=1525367310.2479471.305.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