From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planning out Core Update 117
Date: Tue, 07 Nov 2017 10:44:50 +0000 [thread overview]
Message-ID: <1510051490.4838.300.camel@ipfire.org> (raw)
In-Reply-To: <f2c66516-aa59-3997-d5ba-59157f0e7300@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]
Hi,
On Mon, 2017-11-06 at 22:06 +0100, Matthias Fischer wrote:
> Hi,
>
> On 06.11.2017 19:32, Michael Tremer wrote:
> > Hello,
> >
> > so the big Core Update 115 has been shipped last week. Core Update 116 is
> > coming
> > today. So the next one should be a little bit calmer please :)
>
> We'll see... ;-)
>
> > I do not have anything so far except some smaller bug fixes here and there.
> > Does
> > anyone have anything big? It doesn't have to be another big update. We could
> > also just improve IPFire where ever it is needed with loads of smaller
> > changes
> > and start working on 3 and other sub-projects that are floating around...
>
> Just back in town and getting a grip - I only have a few smaller fixes
> and features in mind:
>
> 'captive portal'-localization: missing german translation for
> 'unlimited' - patch is being prepared.
Okay.
> https://forum.ipfire.org/viewtopic.php?f=17&t=19792 (Mini-Bug in
> 'captive portal'): couldn't test this by now
I fixed this one already:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=ad1204e4eb397b4f7d10c3bdfa9214aa8c0a0575
> Updates in progress: 'ethtool' to 4.13, 'smartmontools' to 6.6, 'tor' to
> 0.3.1.8 (interested?)
Okay. Could you also please review at least some of the patches that Marcel sent
last week?
> 'squid-graph'-localization and package (if I get the time)
>
> As I can see: nothing serious from my side... ;-)
That's good :)
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-07 10:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:32 Michael Tremer
2017-11-06 21:06 ` Matthias Fischer
2017-11-07 10:44 ` Michael Tremer [this message]
2017-11-17 12:59 ` Matthias Fischer
2017-11-17 19:37 ` Matthias Fischer
2017-11-17 21:25 ` Michael Tremer
2017-11-17 23:15 ` Matthias Fischer
2017-11-18 7:44 ` Marcel Lorenz
2017-11-06 21:09 ` Matthias Fischer
2017-11-07 10:46 ` Michael Tremer
2017-11-07 15:05 ` Michael Tremer
2017-11-07 18:41 ` Matthias Fischer
2017-11-07 22:47 ` Michael Tremer
2017-11-21 14:42 ` Michael Tremer
2017-11-21 17:35 ` Matthias Fischer
2017-11-22 16:37 ` Michael Tremer
2018-01-29 13:23 ` Compress images with XZ (was: Planning out Core Update 117) Michael Tremer
2018-01-30 16:47 ` Compress images with XZ Matthias Fischer
2018-01-30 20:03 ` Michael Tremer
2018-02-03 19:44 ` Matthias Fischer
2018-02-03 21:09 ` Matthias Fischer
2018-02-06 1:05 ` Michael Tremer
2018-02-11 15:35 ` Matthias Fischer
2018-02-11 19:57 ` Michael Tremer
2018-05-11 20:27 ` Michael Tremer
2018-05-12 0:35 ` Tom Rymes
2018-05-12 8:48 ` Michael Tremer
2018-05-12 14:14 ` Matthias Fischer
2018-05-12 19:40 ` Michael Tremer
2017-11-10 11:01 ` Planning out Core Update 117 ummeegge
2017-11-10 12:18 ` Michael Tremer
2017-11-10 13:35 ` ummeegge
[not found] <7EA8C1E7-14CC-4906-9688-504DA016795D@gmx.com>
2017-11-10 15:36 ` ummeegge
2017-11-18 20:53 ` Horace Michael
2017-11-21 10:25 ` ummeegge
2017-11-21 11:49 ` Michael Tremer
2017-11-21 12:30 ` Horace Michael
2017-11-22 10:30 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=1510051490.4838.300.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